Security readout for executives and security teams
Plain-English summary
Smart Cleaning for WordPress reportedly allows a subscriber-level user to upload arbitrary files in versions through 4.8.6. Successful abuse could compromise website data, integrity, and availability. Because authentication is required, exposure depends partly on whether untrusted users can obtain or already possess subscriber accounts.
Executive priority
Treat this as an urgent same-day exposure assessment. Prioritize public sites with affected versions and open registration. If exposure is confirmed, contain promptly and investigate for suspicious uploads. No active exploitation is established by the supplied sources, but the potential impact is critical.
Technical view
CVE-2026-74016 is classified as CWE-434 with CVSS 9.9. The vector indicates remote, low-complexity exploitation requiring low privileges, without user interaction, and potentially affecting resources beyond the vulnerable component. The supplied data does not identify the vulnerable upload handler, accepted file types, fixed version, or vendor remediation.
Likely exposure
Likely exposure is highest for internet-accessible WordPress sites running Smart Cleaning 4.8.6 or earlier with public registration, untrusted subscribers, or compromised subscriber accounts. The record’s structured affected-version field says “n/a” and defaults to unaffected, conflicting with the title and description; confirm installed versions directly.
Exploitation context
The source bundle does not establish active exploitation, public proof-of-concept availability, or inclusion in CISA KEV. Authentication as a subscriber is reportedly required, but low complexity and no user interaction make exposed sites important to triage promptly.
Researcher notes
The title and description identify Smart Cleaning through 4.8.6, but the structured affected entry provides no version and defaults to unaffected. This inconsistency lowers certainty. No vulnerable function, endpoint, patch, fixed release, proof of concept, or exploitation telemetry is supplied. Avoid declaring remediation complete until authoritative vendor or Patchstack guidance confirms it.
Mitigation direction
- Identify internet-facing WordPress sites using Smart Cleaning and record their installed versions.
- Check current vendor and Patchstack guidance for an approved fixed version or specific mitigation.
- Temporarily disable the affected theme where operationally acceptable until authoritative remediation is confirmed.
- Restrict public registration and review existing subscriber accounts as interim risk reduction.
- Back up affected sites before remediation and preserve relevant logs for investigation.
Validation and detection
- Confirm whether Smart Cleaning is installed and whether its version is 4.8.6 or earlier.
- Review subscriber accounts for unexpected creation, privilege changes, or suspicious recent activity.
- Inspect WordPress upload and theme-accessible directories for unexpected or executable files.
- Review web and application logs for anomalous authenticated uploads or requests.
- After remediation, verify the affected theme is disabled or updated according to authoritative guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupFile access behavior lookup
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.
Open ATT&CK lookupCVE-2026-74016 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16PatchstackVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/wordpress/theme/smart-cleaning/vulnerability/wordpress-smart-cleaning-theme-4-8-6-arbitrary-file-upload-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.