GHSA-59wm-6vhj-9fgr
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Network CSRF needing no attacker auth (PR:N) but victim interaction (UI:R); JSON hijacking yields limited confidentiality (C:L), forged actions give integrity impact (I:H), no availability effect (A:N).
Primary rating from Vendor (CNA).
CVSS VectorVendor
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Lifecycle Timeline
6Description PRE-NVD
Articles & Coverage 1
AnalysisAI
Cross-site request forgery via JSON Hijacking affects Apache JSPWiki through version 2.12.3, letting a remote attacker who lures an authenticated user to a malicious page read sensitive JSON responses and force state-changing wiki actions in the victim's session. The flaw (CWE-352) is fixed in 2.12.4 and carries a vendor CVSS of 8.8, though exploitation requires user interaction; no public exploit identified at time of analysis and it is not listed in CISA KEV.
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires the victim to be an authenticated JSPWiki user (valid session cookie) who is tricked into visiting an attacker-controlled web page while that session is active - this user interaction (CVSS UI:R) is the key limiting factor. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The vendor CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H = 8.8) rates all three impacts High, which is aggressive for a CSRF/JSON-hijacking issue: CSRF realistically grants integrity impact (actions performed as the victim) and JSON hijacking grants some confidentiality (leaked JSON), but full High confidentiality and any availability impact are not well supported by the description - verify impact scope with the vendor. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker hosts a malicious web page and lures a logged-in JSPWiki user to it (e.g. via a link in email or chat). … |
| Remediation | Vendor-released patch: upgrade to Apache JSPWiki 2.12.4, which fixes the issue and is the primary recommended action per the Apache advisory (https://jspwiki-wiki.apache.org/Wiki.jsp?page=CVE-2026-28813 and the announcement thread https://lists.apache.org/thread/56440mymwkxt1hf3j8hjpo41yco7gotv). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, identify all systems running Apache JSPWiki and assess current versions; notify users that they should avoid clicking suspicious links while authenticated to JSPWiki. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-352 – Cross-Site Request Forgery (CSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-51180