CVE-2023-53933 json
Serendipity 2.4.0 Authenticated Remote Code Execution via File Upload
published 2025-12-17 10 mo ago modified 2026-06-17 4 mo ago also EUVD-2023-60198
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
Serendipity 2.4.0 contains a remote code execution vulnerability that allows authenticated attackers to upload malicious PHP files with .phar extension. Attackers can upload files with system command payloads to the media upload endpoint and execute arbitrary commands on the server.
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 10 mo ago
Exploit prediction
1.02% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- exploit-db.com https://www.exploit-db.com/exploits/51372 referenced PoC, tagged "exploit" by a source, unverified
- vulncheck.com https://www.vulncheck.com/advisories/serendipity-authenticated-remote-code-execution-via-file-upload referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.7 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| CNA | 4.0 | 8.7 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- s9y Serendipity
Classification
- Weakness
-
- CWE-434 Unrestricted Upload of File with Dangerous Type
References
-
exploit-db.com
/exploits/51372
exploit, third-party-advisory, vdb-entry
-
vulncheck.com
/advisories/serendipity-authenticated-remote-code-execution-via-file-upload
third-party-advisory, exploit
-
docs.s9y.org
/
product
Sources
- CVE List CVE-2023-53933
- NVD CVE-2023-53933
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.