Security readout for executives and security teams
Plain-English summary
OpenCart 4.2.0.0 may let a malicious extension place files outside its intended installation folder. This could put attacker-controlled PHP files in the website directory, potentially compromising store data and administrative operations. The source bundle identifies only version 4.2.0.0 as affected.
Executive priority
Treat confirmed OpenCart 4.2.0.0 deployments as an immediate remediation priority, especially internet-facing stores. Restrict extension installation now, investigate suspicious changes, and obtain official vendor guidance. The potential business impact includes website compromise and exposure or manipulation of sensitive commerce data.
Technical view
The extension installer extracts .ocmod.zip archives without confirming that archive paths remain within the extraction directory. Traversal sequences can therefore produce an arbitrary file write, including into the webroot. The issue is classified as CWE-22 with CVSS 3.1 score 9.1, reflecting high confidentiality and integrity impact.
Likely exposure
Prioritize OpenCart 4.2.0.0 systems where untrusted or attacker-supplied extension archives can reach the installer. The provided evidence does not explain installer access controls or how unauthenticated delivery occurs, despite the CVSS vector reporting no privileges or user interaction required.
Exploitation context
The bundle describes a crafted extension writing files such as a PHP web shell into the webroot. It provides no evidence of active exploitation, and the CVE is not listed as KEV in the supplied data. Public exploit availability is not established.
Researcher notes
The core primitive is archive path traversal during extension extraction, resulting in arbitrary file placement. The bundle does not identify a patched version, vendor workaround, affected configuration requirements, public proof of concept, or observed exploitation. Validate environmental preconditions without using malicious payloads on production systems.
Mitigation direction
- Identify and prioritize every OpenCart 4.2.0.0 deployment.
- Check current OpenCart and CERT guidance for an official fix or supported upgrade.
- Until authoritative guidance is available, prevent untrusted extension uploads and installations.
- Restrict installer access to explicitly authorized administrators.
- Preserve logs and investigate unexpected files before restoring affected systems.
Validation and detection
- Confirm deployed OpenCart versions from authoritative inventory and application records.
- Review who can access the extension installer and submit extension archives.
- Compare webroot and application files against trusted release and deployment artifacts.
- Review extension-installation and administrative logs for unexpected activity.
- Confirm mitigations or vendor updates in a non-production environment before rollout.
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-22: 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-18412 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.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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:N/UI:N/S:U/C:H/I:H/A:N3.95.2CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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://kb.cert.org/vuls/id/614868CVE reference, certcc
- https://www.kb.cert.org/vuls/id/614868CVE reference, CVE
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.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.