Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privilege forum user
-
DeliveryPost thread message containing script payload
-
ExploitBody stored and rendered unsanitized by messageListBody.jsp
-
ExecutionVictim opens thread, script executes in browser
-
ImpactSteal session cookies or perform actions as victim
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated forum account (PR:L) capable of posting message bodies, and succeeds specifically because messageListBody.jsp renders those bodies with filter="false" and RenderingFilterManagerImp.java applies non-escaping default filters - i.e. the stored message body is emitted without HTML/script escaping. The payload only fires when another user passively views the affected thread (UI:P / UI:R), so there is no zero-click or unauthenticated path. Limiting factors: attacker needs valid credentials/posting rights, a victim must load the malicious thread, and impact is confined to the browser context of forum users (session/content level), not the server. |
| Impact | This is a medium-severity stored XSS (CWE-79) with a provided CVSS 4.0 score of 5.1, and the signals are internally consistent rather than conflicting. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N) indicates network-reachable but authenticated (PR:L) exploitation that requires passive victim interaction (UI:P) - a victim must view the malicious thread - and yields only low confidentiality and integrity impact with no availability impact, which is typical for reflected session-/content-level script execution rather than full account or server takeover. No EPSS score, KEV listing, or public POC was provided in the input: exploitation status is 'no public exploit identified at time of analysis.' There is no conflict between a high CVSS and low real-world risk here because the CVSS itself is medium; the dominant risk-limiting factors are the authentication requirement and the niche deployment footprint of Jivejdon. The chief missing signals are EPSS probability and any exploitation telemetry - absence of these is not evidence of safety, but combined with the obscure product this reads as a low-priority issue for most organizations unless they specifically run Jivejdon. One caveat to verify: the technical details (filter="false" in messageListBody.jsp and non-escaping default filters in RenderingFilterManagerImp.java) are sourced from the VulnCheck advisory and the linked source lines, not from an independent vendor patch advisory. |
| Exploit ScenarioDerived | An attacker registers or uses an existing low-privilege forum account on a Jivejdon 5.0 instance and posts a forum message whose body contains a JavaScript payload. Because messageListBody.jsp renders the body with filter="false" and non-escaping default filters, the script is stored and later executes in the browser of every authenticated user who opens that thread, enabling session theft or actions-on-behalf. No public exploit code was identified, but the payload is a trivial unsanitized HTML/script injection. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Stored cross-site scripting in Jivejdon through 5.0 allows any authenticated forum user to inject JavaScript into a thread by posting an unsanitized message body, which then executes in the browser of every other user who opens that thread. The flaw arises because messageListBody.jsp renders stored message bodies with filter="false" and RenderingFilterManagerImp.java applies non-escaping default filters, so attacker-supplied HTML/script is emitted verbatim; exploitation requires a valid posting account (PR:L) plus a victim passively viewing the thread (UI:R), and impact stays within the browser/session context of forum users rather than the server. The provided CVSS 4.0 score is 5.1 (medium) and the independent assessment (CVSS 3.1: AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N) is consistent with that rating; no public exploit code was identified at time of analysis and there is no CISA KEV entry.
RemediationAI
No vendor-released patch identified at time of analysis; the supplied references point only to the vulnerable source locations and the upstream issue report, not to a tagged fix release, so administrators of Jivejdon 5.0 and earlier must apply compensating controls. The most direct fix is to change the messageListBody.jsp rendering call from filter="false" to an escaping filter (or remove the filter attribute and rely on default escaping) and to replace the non-escaping default filters registered in RenderingFilterManagerImp.java with an HTML-entity encoder such as OWASP Java Encoder applied to message body output; the trade-off is that forum posts containing intentional HTML markup will render as visible tags or be stripped until a sanitizer (for example OWASP Java HTML Sanitizer with an allow-list) is layered in. Until that code change is deployed, restrict message-posting rights to trusted accounts (reduces but does not eliminate exposure, since any legitimate account can still be abused), and deploy a Content-Security-Policy header that forbids inline script (script-src 'self' without 'unsafe-inline') on forum pages to blunt execution of injected payloads, accepting that this may break inline scripts the theme relies on. Edge WAF/DLP rules that strip <script> and event-handler attributes from POSTed message bodies provide a stopgap but are trivially bypassed by obfuscated encodings, and reading-thread pages should still be treated as untrusted. Monitor the upstream repository at https://github.com/banq/jivejdon and the VulnCheck advisory (https://www.vulncheck.com/advisories/jivejdon-through-5.0-stored-xss-via-messagelistbody-jsp-forum-message-rendering) for a tagged patched version, and re-scan stored message content for injected script once a fix is available.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Jivejdon is a Java-based discussion forum (Jdon framework) whose storage and rendering layers are split across a JSP view and a Java rendering layer. Per the referenced source, message bodies are written to the datastore and later redisplayed by application/thread/messageListBody.jsp (lines 136-138) with filter="false", which explicitly disables the view-layer output filtering, while src/main/java/com/jdon/jivejdon/domain/model/message/output/RenderingFilterManagerImp.java (lines 48-49) registers default rendering filters that perform no HTML/script escaping. The result is a classic CWE-79 stored/persistent XSS: untrusted content is persisted on the first request and only neutralized (or not) at render time, so the injection is replayed to every subsequent reader of the thread without any further attacker action. Because the payload travels through the forum's normal message-posting path, it bypasses the assumption that stored content is trusted, and the CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:P) confirms the attacker needs a low-privileged account while the victim's participation is passive. Under the CPE cpe:2.3:a:banq:jivejdon:*:*:*:*:*:*:*:* no version constraint is expressed, meaning all released builds up to and including 5.0 are treated as affected by the source data.
Know when Jivejdon gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N
Authenticated posting rights give PR:L, victim must view the thread so UI:R, stored XSS crosses into the victim browser context giving S:C with low C/I and no availability impact.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
Jivejdon through 5.0 contains a stored cross-site scripting vulnerability that allows authenticated attackers to inject script by posting unsanitized forum message bodies. Message bodies are rendered by messageListBody.jsp with filter="false" and non-escaping default filters, executing script in the browser of every user viewing the thread.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Jivejdon through 5.0 stores account passwords as unsalted MD5 digests - computed by ToolsUtil.hash() and persisted throu
Missing rate limiting in Jivejdon's unauthenticated /account/smsVRAction endpoint allows remote attackers to send unlimi
SQL injection in Jivejdon through 5.0 allows an authenticated user with the Admin role to read arbitrary database conten
Authentication bypass in Jivejdon through 5.0 allows remote attackers to log in as any user whose account was created th
Authenticated users can delete other users' subscriptions in Jivejdon through 5.0 by sending a delete action with a vict
Reflected cross-site scripting in Jivejdon from commit 5489372d through ee67a65e allows unauthenticated remote attackers
Missing authorization in Jivejdon's UpdateThreadToForumAction (present from commit d58a36b0 through commit ee67a65e) let
Reflected cross-site scripting in Jivejdon through 5.0 lets an attacker execute arbitrary JavaScript in an authenticated
Cross-site request forgery in Jivejdon through 5.0 allows unauthenticated attackers to trick authenticated users into de
Stored cross-site scripting in Jivejdon through 5.0 allows an authenticated user to embed script inside a private short
Stored cross-site scripting in Jivejdon through 5.0 lets an authenticated, upload-capable user store an attachment whose
Stored cross-site scripting in the JiveJdon forum platform (banq/jivejdon) from commit 595d8d22 through commit ee67a65e
EUVD-2026-95305
GHSA-3x3v-g28r-qvqh
NVD
CVE.org
EPSS
Exploit-DB