Security readout for executives and security teams
Plain-English summary
A logged-in WordPress subscriber may be able to upload arbitrary files through Warehouse Cargo 2.6.9 or earlier. Successful abuse could compromise website data, content, or availability. The supplied evidence does not explain where files are stored, whether they execute, or whether a corrected release exists.
Executive priority
Treat affected internet-facing sites as an immediate remediation priority because low-privilege accounts may reach a critical file-upload flaw. Quickly establish theme deployment and version scope, reduce subscriber access, and obtain confirmed remediation guidance. Begin incident review if suspicious accounts or files are discovered.
Technical view
CVE-2026-74018 is a CWE-434 unrestricted file-upload vulnerability affecting the WordPress Warehouse Cargo theme through version 2.6.9. CVSS 3.1 rates it 9.9: network-accessible, low complexity, low privileges, no user interaction, changed scope, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely on reachable WordPress sites running Warehouse Cargo 2.6.9 or earlier where an attacker can obtain subscriber access. Open registration and compromised subscriber accounts increase risk. The sources do not establish whether inactive theme installations are exploitable.
Exploitation context
The supplied bundle does not identify this CVE as KEV and provides no evidence of active exploitation. Exploitation requires subscriber-level privileges according to the description. No public indicators, exploit mechanics, or attack telemetry are included, so real-world exploitation prevalence remains unknown.
Researcher notes
The record supplies a vulnerability class, privilege requirement, affected version ceiling, and CVSS vector, but no endpoint, upload validation flaw, file location, execution condition, indicators, or fixed version. Avoid assuming remote code execution without further evidence. The affected-product metadata also reports a default status of unaffected, creating ambiguity that warrants vendor verification.
Mitigation direction
Identify every WordPress instance using Warehouse Cargo and record the installed theme version.
Check vendor and Patchstack guidance for a confirmed patched release or official workaround.
Until guidance is confirmed, restrict subscriber registration and remove unnecessary subscriber accounts.
Consider disabling or removing the affected theme after testing business impact.
Preserve relevant logs and backups before remediation to support incident review.
Validation and detection
Confirm whether Warehouse Cargo 2.6.9 or earlier exists on any reachable WordPress site.
Review user lists for unexpected or recently created subscriber accounts.
Inspect application, web, and file-change records for suspicious uploads or executable files.
Verify the deployed version and repeat integrity checks after following confirmed vendor guidance.
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 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
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical 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.