JspwikiApplication · Apache
CVE-2022-28731
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 carefully crafted request on UserPreferences.jsp could trigger an CSRF vulnerability on Apache JSPWiki before 2.11.3, which could allow the attacker to modify the email associated with the attacked account, and then a reset password request from the login page.
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 confidenceCSRF vulnerability in Apache JSPWiki's UserPreferences.jsp allows attackers to craft malicious requests that modify the email address associated with a victim's account. By changing the email, the attacker can then trigger a password reset from the login page, leading to account takeover.
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.11.3CVSS 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
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 versionLocate the installed Apache JSPWiki version. Check the application header, about page, or version file in the JSPWiki installation directory.Affected if The installed version is below 2.11.3
-
Verify UserPreferences functionality is enabledNavigate to the UserPreferences page in JSPWiki (typically at /JSPWiki/EditPreferences.jsp or similar path) while logged in as an authenticated user.Affected if The UserPreferences page loads and allows modification of account settings including email address
-
Inspect form for CSRF protectionView the HTML source of the UserPreferences.jsp form and examine whether the form submission includes a CSRF token, anti-CSRF token, or similar security token in the request parameters.Affected if The form submission lacks CSRF tokens or anti-CSRF mechanisms
Environment is affected if JSPWiki version is below 2.11.3 and the UserPreferences form is accessible without CSRF token protection.
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.11.3
Upgrade to Apache JSPWiki version 2.11.3 or later. As a temporary workaround, disable the UserPreferences functionality or implement CSRF tokens on the affected form.
2.11.3
- 1. Back up the current JSPWiki installation, database, and configuration files
- 2. Download Apache JSPWiki version 2.11.3 or later from the official Apache JSPWiki distribution (https://jspwiki-wiki.apache.org/)
- 3. Stop the running JSPWiki service
- 4. Replace the existing JSPWiki files with the new version, preserving custom configurations
- 5. Start the JSPWiki service
- 6. Verify the application is functioning correctly by logging in and checking user preferences
- 7. Confirm the CSRF protection is now in place for UserPreferences.jsp
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Jspwiki
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28731 — 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-2022-28731 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