JspwikiApplication · Apache
CVE-2024-27136
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 · uneditedXSS in Upload page in Apache JSPWiki 2.12.1 and priors allows the attacker to execute javascript in the victim's browser and get some sensitive information about the victim. Apache JSPWiki users should upgrade to 2.12.2 or later.
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 confidenceApache JSPWiki 2.12.1 and prior versions contain a stored or reflected Cross-Site Scripting (XSS) vulnerability in the file Upload functionality. An attacker can inject malicious JavaScript code into file upload parameters, which then executes in the victim's browser when the uploaded content is viewed or accessed, enabling session hijacking, credential theft, or sensitive information disclosure.
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
JspwikiApplication
< 2.12.2CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 JSPWiki installation and versionLocate the JSPWiki deployment (check webapp directory, application server, or run 'java -jar jspwiki.war' and look for version info in the UI footer or about pageAffected if Installed version is Apache JSPWiki 2.12.1 or any version prior to 2.12.2
-
Confirm file upload feature is accessibleNavigate to the Upload page in JSPWiki (typically /Upload.jsp or through the Attachments link in the wiki) and verify the file upload form is accessible to usersAffected if The upload functionality is enabled and reachable without authentication errors
-
Check for uploaded files with embedded scriptsReview files in the JSPWiki attachments directory (commonly under /pages/ or /attach/ in the data directory) for suspicious filenames containing script tags or javascript: URIsAffected if Any uploaded files have names containing <script>, javascript:, onload, onerror, or other XSS payloads
-
Inspect recent upload activity logsCheck JSPWiki log files (通常在 logs/ 目录下) for entries showing recent file uploads, paying attention to upload requests with unusual filename patternsAffected if Recent uploads contain encoded or plaintext XSS vectors in filenames or metadata
You are affected if JSPWiki version is 2.12.1 or earlier AND the file upload functionality is accessible and has been used, as the XSS payload would execute when those files are viewed or linked.
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.12.2
Upgrade Apache JSPWiki to version 2.12.2 or later to patch the XSS vulnerability in the Upload page.
2.12.2 or later
- Backup your current JSPWiki installation, including the web application directory and all data files
- Download Apache JSPWiki version 2.12.2 or later from the official Apache distribution site (https://jspwiki.apache.org/)
- Stop the JSPWiki service or application server
- Replace the existing JSPWiki web application files with the new version files
- Review the release notes and migrate any necessary configuration changes
- Start the JSPWiki service or application server
- Verify the upgrade by logging in and testing the upload functionality
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Jspwiki
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing4.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 $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27136 — 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-2024-27136 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