CVE-2026-36761
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 stored cross-site scripting (XSS) vulnerability in the /msg/msgInner/save endpoint of JeeSite v5.15.1 allows attackers to execute arbitrary web scripts or HTML via injecting a crafted input into the msgContent parameter.
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 confidenceA stored cross-site scripting (XSS) vulnerability exists in the /msg/msgInner/save endpoint of JeeSite v5.15.1. The msgContent parameter accepts unsanitized input, allowing attackers to inject malicious JavaScript or HTML that persists in the application and executes when other users view the message content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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 JeeSite installation and versionLocate JeeSite installation directories and check version files (such as pom.xml, version.properties, or application configuration files that contain version metadata). Compare the installed version to v5.15.1.Affected if The installed version is JeeSite v5.15.1 or if version identification confirms the specific vulnerable release.
-
Verify the message module is enabledCheck if the /msg/ message module is deployed and accessible in the JeeSite application. Attempt to access the message functionality or review the application's deployed module list.Affected if The message module (msg) is deployed and active in the application.
-
Confirm the save endpoint is accessibleAttempt to access or trace the /msg/msgInner/save endpoint in the application. Review application routing configuration or web.xml to confirm this endpoint exists and is mapped.Affected if The /msg/msgInner/save endpoint exists and is reachable in the application.
-
Inspect message content storage for malicious payloadsQuery the database table that stores message content (typically related to msgInner or message tables) and examine the msgContent field for unsanitized HTML or script tags such as <script>, <img onerror>, or javascript: URIs.Affected if The msgContent field contains persisted HTML or script tags that were not sanitized or encoded upon storage.
A user is affected if they are running JeeSite v5.15.1 with the message module enabled and the /msg/msgInner/save endpoint accessible, and if the msgContent parameter accepts and stores unsanitized input that could contain malicious scripts.
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 dataImplement strict input validation on the msgContent parameter to reject HTML/script tags, and apply contextual output encoding when the content is rendered to prevent script execution.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36761 — 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-2026-36761 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