CVE-2026-36767
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 · uneditedA path traversal vulnerability in the /content/images/add endpoint of shopizer v3.2.5 allows attackers write arbitrary files to any writeable path via a crafted POST request.
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 confidenceA path traversal vulnerability exists in shopizer v3.2.5 at the /content/images/add endpoint. The endpoint fails to properly validate or sanitize file paths in POST requests, allowing attackers to use '..' sequences or absolute paths to write files outside the intended upload directory to any writable location on the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 shopizer installation and versionLocate the shopizer application in your environment. Check the application's pom.xml, build.gradle, or the compiled WAR/JAR files for the version identifier. Look for files like pom.xml in the root directory, or check the deployed artifact's name/version metadata.Affected if The installed version matches v3.2.5 or falls within an unknown range that includes this vulnerable release.
-
Verify the /content/images/add endpoint exists and is accessibleCheck if the shopizer web application exposes the /content/images/add endpoint. This may be visible in the application's routing configuration, or you can attempt a simple HTTP request to this path (without sending malicious payload) to confirm the endpoint responds.Affected if The endpoint responds to HTTP requests, indicating it is actively enabled in the application.
-
Confirm endpoint lacks authentication enforcementReview the application's security configuration files (such as Spring Security XML or Java configuration) to check if /content/images/add is listed as a permitted anonymous endpoint. Alternatively, observe whether unauthenticated requests to this endpoint return a 200 or 401/403 response.Affected if The endpoint accepts requests without requiring valid authentication credentials.
-
Identify writable directories on the serverExamine the server's file system permissions and deployment configuration. Check the upload directory configuration in shopizer (typically found in application properties under content.images.upload.path or similar), and verify which directories the application process has write access to.Affected if The application has write access to directories outside the intended upload folder, allowing path traversal to escape the upload directory.
A user is affected if running shopizer v3.2.5 with the /content/images/add endpoint exposed and accessible without authentication, where the server filesystem has writable directories that could be reached via path traversal sequences.
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.
From vendor dataRestrict file upload functionality to only accept filenames within an allowed directory by implementing strict whitelist validation of file names, enforcing the upload directory as the only writable location, and rejecting any path traversal sequences (../) or absolute paths in the filename parameter.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,536.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36767 — 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-2026-36767 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