Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-36767: Arbitrary File Write via Path Traversal in Shopizer /content/images/add

Published Apr 30, 2026 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS10.0Critical · v3.1
EPSS0.41%36th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-36767CWE-22 · Improper Limitation of a Pathname…

CVE-2026-36767 is a path traversal vulnerability in Shopizer v3.2.5 affecting the /content/images/add endpoint. According to the provided content, a crafted POST request can abuse path traversal in this endpoint to cause the application to write attacker-controlled files to arbitrary writable paths on the underlying system. The issue is classified as CWE-22. Based on the available information, the flaw stems from insufficient restriction of user-supplied path input during file upload or image handling, enabling traversal outside the intended storage directory and arbitrary file placement.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to write arbitrary files to any path writable by the Shopizer process. This can compromise integrity by overwriting or planting application files, configuration files, or web-accessible content; compromise confidentiality depending on follow-on access enabled by planted files; and affect availability by corrupting application state or critical files. Given the provided CVSS vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H), the vulnerability is remotely exploitable with low complexity, requires no privileges or user interaction, and can have high impact across confidentiality, integrity, and availability.

Mitigation

If you can’t patch tonight, do this now.

If an official fix is not yet available, restrict or disable access to the /content/images/add endpoint, especially from untrusted networks. Place the application behind authentication or network filtering where possible. Run Shopizer with the least privileges necessary so the service account cannot write to sensitive filesystem locations. Constrain writable directories, harden filesystem permissions, and monitor for unexpected file creation or modification in application, webroot, and configuration paths. Web application firewall rules or reverse-proxy filtering may help block suspicious POST requests containing traversal patterns, though this is only a compensating control.

Remediation

Patch, then assume compromise.

Upgrade to a Shopizer version that fixes CVE-2026-36767, if a vendor patch is available. The vulnerable /content/images/add endpoint should be corrected to canonicalize and strictly validate file paths, reject traversal sequences, and enforce writes only within a dedicated upload directory. Server-side controls should generate destination filenames rather than trusting client-supplied paths, and the application should verify the resolved canonical path remains within an allowlisted base directory before writing files.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-36767 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2026-36767 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-36767?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2026-36767.
Is there a patch for CVE-2026-36767?
Upgrade to a Shopizer version that fixes CVE-2026-36767, if a vendor patch is available. The vulnerable /content/images/add endpoint should be corrected to canonicalize and strictly validate file paths, reject traversal sequences, and enforce writes only within a dedicated upload directory.
How severe is CVE-2026-36767?
CVE-2026-36767 has a CVSS v3.1 score of 10.0 (Critical) and an EPSS score of 0.41% (36th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.