JspwikiApplication · Apache
CVE-2019-0224
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 · uneditedIn Apache JSPWiki 2.9.0 to 2.11.0.M2, a carefully crafted URL could execute javascript on another user's session. No information could be saved on the server or jspwiki database, nor would an attacker be able to execute js on someone else's browser; only on its own browser.
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 reflected cross-site scripting (XSS) vulnerability in Apache JSPWiki versions 2.9.0 to 2.11.0.M2 allows execution of malicious JavaScript through specially crafted URLs. The attack is reflected (not stored) and requires tricking a user into clicking a malicious link.
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.9.0, <= 2.10.5= 2.11.0CVSS 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.0/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 version from application filesLocate the JSPWiki installation directory and check the version file or manifest. Common locations include WEB-INF/web.xml, WEB-INF/lib/*.jar filenames, or a version.properties file in the JSPWiki distribution.Affected if The installed version falls within >= 2.9.0 to <= 2.10.5, or equals exactly 2.11.0.
-
Check the JSPWiki web interface accessibilityDetermine if the JSPWiki web application is running and accessible over HTTP/HTTPS by accessing the application's base URL.Affected if The web interface is exposed and accessible to users who could be tricked into clicking malicious links.
-
Inspect HTTP responses for version disclosureSend a request to the JSPWiki application and examine the Server header or any version information returned in HTML meta tags, footers, or error pages.Affected if The response reveals a JSPWiki version number matching the affected range.
-
Review application logs for version startup messagesExamine JSPWiki log files for startup messages that display the version number during application initialization.Affected if Logs confirm a startup version within the affected range.
A user is affected if JSPWiki version 2.9.0 through 2.10.5 or exactly version 2.11.0 is running and its web interface is accessible to users who could be tricked into clicking crafted URLs.
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 dataUpgrade to Apache JSPWiki 2.11.0.M3 or later, which contains the patch for this vulnerability. As a workaround, implement URL input validation and output encoding at the application or WAF layer.
Fix this in Jspwiki
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0224 — 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-2019-0224 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