CVE-2022-34254
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAdobe Commerce versions 2.4.3-p2 (and earlier), 2.3.7-p3 (and earlier) and 2.4.4 (and earlier) are affected by an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability that could be abused by an attacker to inject malicious scripts into the vulnerable endpoint. A low privileged attacker could leverage this vulnerability to read local files and to perform Stored XSS. Exploitation of this issue does not require user interaction.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAdobe Commerce (Magento) contains a path traversal vulnerability in versions 2.4.3-p2 and earlier, 2.3.7-p3 and earlier, and 2.4.4 and earlier. The flaw allows low-privileged authenticated attackers to inject malicious scripts via path traversal, enabling local file disclosure and stored XSS without user interaction.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2.3.0, < 2.3.7>= 2.4.0, < 2.4.3= 2.3.7= 2.4.3= 2.4.4>= 2.3.0, < 2.3.7>= 2.4.0, < 2.4.3= 2.3.7= 2.4.3= 2.4.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Adobe Commerce/Magento versionRun 'bin/magento --version' from the installation root, or check the version in composer.json, or view the version in the admin panel footerAffected if Version matches 2.4.3-p2 or earlier, 2.3.7-p3 or earlier, or exactly 2.4.4
-
Confirm CMS module is installed and enabledRun 'bin/magento module:status Magento_Cms' or check app/etc/config.php for 'Magento_Cms' set to 1Affected if Magento_Cms module reports as enabled or present in config.php with value 1
-
Verify user authentication mechanism is accessibleCheck if the frontend/customer account creation or login is functional at /customer/account/create or /customer/account/loginAffected if Low-privileged user accounts can be created or accessed in the system
If the installed version falls within 2.3.0 to 2.3.7-p3, 2.4.0 to 2.4.3-p2, or exactly 2.4.4 AND the CMS module is enabled AND low-privileged user access exists, the environment is affected by this path traversal vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.3.72.4.3
Apply the vendor-released security patch or upgrade Adobe Commerce to the patched version (2.4.3-p3 or 2.3.7-p4 or later) per Adobe's security bulletin.
Adobe Commerce 2.4.4 or later / 2.3.7-p3 or later
- Backup the Adobe Commerce/Magento database and files
- Upgrade Adobe Commerce to version 2.4.4 or later (or 2.3.7-p3 or later for the 2.3.x branch)
- Clear the cache after upgrade (bin/magento cache:flush)
- Verify the upgrade was successful and test core functionality
- Ensure the version is now patched by checking composer.json or admin panel
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34254 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-34254 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data