The Security & Malware scan by CleanTalk plugin for WordPress is vulnerable to arbitrary file uploads due to the plugin uploading and extracting .zip archives when scanning them for malware through the checkUploadedArchive() function in all versions up to, and including, 2.149. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.
Security readout for executives and security teams
Plain-English summary
This is a critical WordPress plugin flaw that could let an unauthenticated internet attacker upload arbitrary files to an affected site. Because uploaded files may enable remote code execution, compromised sites could be defaced, used for malware hosting, or become an entry point into connected systems.
Executive priority
Handle as urgent for any internet-facing WordPress property using this plugin. Even without confirmed active exploitation, the unauthenticated upload path and possible remote code execution make delay high risk.
Technical view
The issue is CWE-434 arbitrary file upload in CleanTalk’s WordPress security plugin. Sources describe the checkUploadedArchive() function uploading and extracting ZIP archives during malware scanning in versions up to and including 2.149, without requiring authentication. Impact may include remote code execution depending on server configuration.
Likely exposure
Exposure is likely limited to WordPress sites running the named CleanTalk security/malware plugin at version 2.149 or earlier. The source bundle has inconsistent product naming, so validate by plugin slug, installed version, and vendor advisory references.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source here confirms active exploitation. However, the conditions are severe: network reachable, low complexity, no privileges, no user interaction, and potential full confidentiality, integrity, and availability impact.
Researcher notes
Analysis is limited to the supplied CVE bundle. The bundle identifies the vulnerable function and version range but does not provide exploit details, confirmed exploitation, or a fully explicit fixed version. Product naming should be cross-checked during asset validation.
Mitigation direction
Update the CleanTalk plugin to a version outside the vulnerable range.
If update status is unclear, follow CleanTalk or WordPress plugin repository guidance.
Temporarily disable or remove the plugin if remediation cannot be verified.
Review affected servers for unexpected uploaded or extracted files.
Prioritize cleanup and credential rotation if compromise indicators are found.
Validation and detection
Inventory WordPress sites for the CleanTalk plugin and installed version.
Treat versions up to and including 2.149 as vulnerable.
Check plugin slug and names against the WordPress Trac reference.
Review web and application logs for unauthenticated archive upload activity.
Inspect upload and plugin directories for unexpected executable files.
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.
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.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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
4Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
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.
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.