Skip to main content
Menu
CVEs

CVE

bolo-solo stored XSS in comment reply-to names

CVE-2026-129492EUVD-2026-126156GHSA-WXCP-24FM-4F4C

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

5.3MediumCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported
Published
Last modified
Reference
Last checked
0.21% · 11th percentile
17/100 · provisional
1 proof of concept on GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

Bolo (bolo-solo) from bolo-blog, versions 1.7 through 2.6.4, has a stored cross-site scripting flaw in how comment reply-to names are handled. An attacker can reach it remotely, without logging in, by posting a comment with a short script that runs in visitors' browsers when they view it, which can steal session cookies that are not marked HttpOnly and take over administrator accounts.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

Bolo (bolo-solo) 1.7 through 2.6.4 contains a stored cross-site scripting vulnerability that allows unauthenticated attackers to inject scripts via the unsanitized commentOriginalCommentName parameter. Attackers can post a comment to /article/comments with a short payload that steals non-HttpOnly session cookies from visitors, enabling takeover of administrator accounts.

cve.now Index

17Pcve.now Index 17 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.3/10CVSS 5.3
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 72 if added to CISA KEV
  • Would score about 67 if CISA's SSVC rates exploitation active
  • Would score about 32 if advisories confirm default setups are exposed

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129492 (Bolo (bolo-solo) 1.7 through 2.6.4 Stored XSS via Comment Reply-To Name), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129492 (entry last updated 2026-11-16):
Affected:
- bolo-blog bolo-solo: from 1.7, through 2.6.4
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129492 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129492 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/bolo-blog/bolo-solo/issues/331
- https://vul.yulun.ac.cn/20261115/bolo-solo/
- https://github.com/bolo-blog/bolo-solo/blob/e0ab6b1f57a4ba66b4a42a7b6ceafb87c33290cc/src/main/java/org/b3log/solo/service/CommentMgmtService.java#L299-L306
- https://github.com/bolo-blog/bolo-solo/blob/e0ab6b1f57a4ba66b4a42a7b6ceafb87c33290cc/src/main/webapp/skins/bolo-nexmoe/common-comment.ftl#L29-L34
- https://www.vulncheck.com/advisories/bolo-bolo-solo-1.7-through-2.6.4-stored-xss-via-comment-reply-to-name
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129492
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129492"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • bolo-blog bolo-solo

    From 1.7 · through 2.6.4

Evidence 8

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Public exploit code · 1

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

  1. Exploit

Other links · 5

  1. Report
  2. Repository
  3. Repository
  4. Link
  5. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129492

Is CVE-2026-129492 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-129492?

bolo-solo: from 1.7 through 2.6.4.Source: cve.now feed data