CVE-2020-10964
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSerendipity before 2.3.4 on Windows allows remote attackers to execute arbitrary code because the filename of a renamed file may end with a dot. This file may then be renamed to have a .php filename.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSerendipity before 2.3.4 on Windows contains a file renaming vulnerability where an uploaded file can have a trailing dot in its filename. When the file is subsequently renamed, the .php extension can be appended, allowing arbitrary PHP code execution on the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.3.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Serendipity is installedLocate the Serendipity installation directory - look for files like serendipity_config_local.inc.php, serendipity_config.inc.php, or the characteristic index.php with Serendipity codeAffected if Serendipity is present on the system
-
Identify installed Serendipity versionOpen the main configuration file (serendipity_config_local.inc.php or similar) and locate the version entry, or access the admin dashboard and navigate to the About/System Info sectionAffected if Version is below 2.3.4 (e.g., 2.3.3, 2.3.2, etc.)
-
Determine the operating systemCheck the server OS environment - query system information via command (uname -a on Linux, systeminfo on Windows) or inspect web server configurationAffected if The web server is running Windows (the vulnerability only affects Windows)
-
Verify file upload functionality is enabledLog into the Serendipity admin panel and navigate to the Media Library or Upload section - check if the upload feature is accessible and not disabled in configurationAffected if File uploads are enabled and users can upload files through the media library
The environment is affected if Serendipity version is below 2.3.4, the server OS is Windows, and file upload functionality is enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.3.4
Upgrade Serendipity to version 2.3.4 or later. Additionally, implement strict file upload validation that strips trailing dots from filenames and explicitly blocks .php/.phtml extensions in upload functionality.
Serendipity 2.3.4
- Upgrade Serendipity to version 2.3.4 or later
- After upgrade, verify the installation is working correctly
- Test file upload functionality to confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10964 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-10964 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data