LiveActive security incident?Get immediate response
CVE Record

CVE-2020-10964: Serendipity before 2.3.4 on Windows allows remote attackers to execute arbitrary code because the filename...

Serendipity 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This issue affects Serendipity on Windows before version 2.3.4. A remote attacker could abuse file renaming behavior to turn a file into a PHP file and execute code. The sources do not provide CVSS scoring or evidence of active exploitation.

Executive priority

Treat this as high priority for any Windows-hosted Serendipity site because the stated impact is arbitrary code execution. Urgency depends on whether the organization runs Serendipity before 2.3.4 and exposes relevant file-management functionality.

Technical view

CVE-2020-10964 describes remote code execution in Serendipity before 2.3.4 on Windows. The weakness involves filenames ending with a dot during rename operations, allowing a later rename to a .php filename. Public metadata lacks CWE, CVSS, and detailed affected CPE data.

Likely exposure

Exposure is most likely for Windows-hosted Serendipity deployments running versions before 2.3.4, especially where remote users can reach file upload or rename functionality. The source bundle does not identify affected CPEs or specific configurations beyond Windows and pre-2.3.4 versions.

Exploitation context

The CVE description supports remote code execution potential. The record is not listed as KEV, and the provided sources do not state active exploitation, public exploit availability, or observed attacks.

Researcher notes

The public record is sparse: no CVSS, CWE, CPE, exploit-status detail, or configuration matrix is included. Analysis should stay anchored to Windows, Serendipity before 2.3.4, and the rename-to-PHP behavior described in the CVE.

Mitigation direction

  • Upgrade Windows-hosted Serendipity deployments running versions before 2.3.4 to 2.3.4 or later.
  • Review the Serendipity 2.3.4 security update and release notes for vendor guidance.
  • Prioritize instances where untrusted users can rename uploaded files or manage media.
  • If version status is unknown, verify it before allowing internet-facing administrative access.

Validation and detection

  • Inventory Serendipity installations and record version and hosting operating system.
  • Confirm no Windows-hosted instance runs Serendipity before 2.3.4.
  • Review user roles that can upload, rename, or manage files.
  • Check web roots and media paths for unexpected PHP files created near the disclosure period.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-10964 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.