LiveActive security incident?Get immediate response
CVE Record

CVE-2020-25213: The File Manager (wp-file-manager) plugin before 6.9 for WordPress allows remote attackers to upload and ex...

The File Manager (wp-file-manager) plugin before 6.9 for WordPress allows remote attackers to upload and execute arbitrary PHP code because it renames an unsafe example elFinder connector file to have the .php extension. This, for example, allows attackers to run the elFinder upload (or mkfile and put) command to write PHP code into the wp-content/plugins/wp-file-manager/lib/files/ directory. This was exploited in the wild in August and September 2020.

CriticalCVSS 10Known exploitedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A vulnerable WordPress File Manager plugin version before 6.9 could let an unauthenticated attacker take control of a site by uploading and running server-side code. This was exploited in the wild and is listed in CISA KEV, so exposed legacy installations should be treated as potentially compromised.

Executive priority

Prioritize immediate remediation and compromise assessment for any affected public WordPress site. This is a known-exploited, unauthenticated RCE with full confidentiality, integrity, and availability impact, making delayed action high business risk.

Technical view

CVE-2020-25213 is an unauthenticated remote code execution issue in wp-file-manager before 6.9. An unsafe elFinder example connector was exposed as PHP, enabling arbitrary PHP file upload/write and execution. The CVE maps to CWE-434 and carries CVSS 3.1 score 10.0.

Likely exposure

Internet-facing WordPress sites with the File Manager plugin wp-file-manager installed below version 6.9 are the primary exposure. Risk is highest where the plugin remained active during or after the 2020 exploitation window.

Exploitation context

The source bundle states exploitation occurred in August and September 2020. CISA KEV also lists CVE-2020-25213 as known exploited. Public reporting cited large-scale probing and attacks, but the bundle does not prove current active exploitation volume.

Researcher notes

Evidence is strong for historical exploitation and affected version scope, but the bundle does not provide current exploit telemetry. Avoid assuming only defacement risk; arbitrary PHP execution can support persistence, data theft, lateral movement, or infrastructure abuse after initial compromise.

Mitigation direction

  • Upgrade wp-file-manager to version 6.9 or later using vendor guidance.
  • Disable or remove the plugin if it is not business-critical.
  • Treat previously exposed vulnerable sites as potentially compromised.
  • Review vendor advisories before making assumptions about complete remediation.
  • After remediation, rotate credentials exposed to the affected WordPress host.

Validation and detection

  • Inventory all WordPress sites for wp-file-manager installation and version.
  • Confirm no active instance runs wp-file-manager below 6.9.
  • Review web roots and plugin directories for unexpected PHP files.
  • Check web server logs for suspicious plugin access during relevant exposure windows.
  • Verify no unauthorized WordPress admin users or persistence mechanisms remain.
Prepared
Confidence
high
Sources
9

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.

cwe · medium confidence lookup

CWE-434: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-25213 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
Critical
CVSS
10 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:C/UI:N

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.

1CVSS vectors
0Timeline events
0ADP providers
9Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
10CVSS 3.1CriticalCVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:C/UI:N3.96Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

10Critical
CVSS 3.1 vector shape for CVE-2020-25213Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:C/UI:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-434 · source CWE mapping

Unrestricted Upload of File with Dangerous Type

Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.