CVE-2026-11467
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 security vulnerability has been detected in jishenghua jshERP up to 3.6. This vulnerability affects the function addAccountHeadAndDetail of the file jshERP-boot/src/main/java/com/jsh/erp/service/AccountHeadService.java of the component addAccountHeadAndDetail Endpoint. Such manipulation of the argument fileName leads to path traversal. The attack can be executed remotely. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.
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 · moderate confidencePath traversal vulnerability in jshERP's addAccountHeadAndDetail endpoint allows remote attackers to manipulate the fileName parameter with directory traversal sequences (e.g., ../../) to write files to arbitrary locations on the server. The vulnerability exists in AccountHeadService.java where user-supplied filename input is not properly validated or sanitized before file operations.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
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.
-
Confirm jshERP installation and versionLocate the jshERP application in your environment and identify its version by checking deployment manifests, pom.xml, or application metadata filesAffected if The installed version of jshERP matches the version range containing the vulnerable AccountHeadService.java component
-
Locate AccountHeadService.java in the deploymentSearch the deployed application files for AccountHeadService.java, typically found under src/main/java in the ERP source or decompiled in the deployed WAR/WEB-INF directoryAffected if The file exists and contains the addAccountHeadAndDetail function
-
Verify fileName parameter handling in addAccountHeadAndDetailInspect the addAccountHeadAndDetail function code to examine how the fileName parameter is processed - look for any input validation, sanitization, or path resolution logic applied to this parameterAffected if The code directly uses the fileName parameter without validation or contains path traversal sequences (../, ..\) in the logic without rejection mechanisms
-
Check if AccountHead endpoint is accessibleDetermine if the HTTP endpoint exposing addAccountHeadAndDetail is exposed by checking application routing configuration, typically mapped to account-related API paths in jshERPAffected if The endpoint is reachable over the network without additional authentication beyond low-privilege user access
You are affected if jshERP is deployed with the vulnerable AccountHeadService.java containing addAccountHeadAndDetail that processes a fileName parameter without rejecting 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 dataImplement strict input validation on the fileName parameter to reject directory traversal sequences and path characters. Store uploaded files in a secure, non-executable directory with randomized filenames, and use allowlist validation for permitted characters.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11467 — 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-11467 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