CVE
bolo-solo information disclosure of article passwords via /articles
Affects Bolo (bolo-solo) 1.7 through 2.6.4 on blogs with at least one article that has a view password. No fixed version is listed in the checked facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- Exploited
- Proof of concept public, per CISA
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The checked facts name no workaround or mitigation. The exposed data is article view passwords, but the facts do not say how to limit that exposure.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.48% · 42nd percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 49/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
- Exploitation: poc
- Automatable: yes
- Technical impact: partial
Summary
Bolo (bolo-solo) versions in the affected range expose article view passwords through the public /articles endpoint, which returns the plaintext password for password-protected articles. A remote attacker who needs no login can read those passwords and use them to open the protected article content.
Original description
Bolo (bolo-solo) 1.7 through 2.6.4 contains an information disclosure vulnerability that allows unauthenticated attackers to read article view passwords via the public GET /articles endpoint. Attackers can retrieve the plaintext articleViewPwd field returned by ArticleProcessor.getArticlesByPage and submit it to read password-protected article content.
Who should check
Teams running bolo-solo 1.7 through 2.6.4 (bolo-blog) that publish password-protected articles on a public blog.
“Affecting bolo-solo >= 1.7, <= 2.6.4”
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch5/5No patch listed yet
What would change the score
- Would score about 79 if added to CISA KEV
- Would score about 74 if CISA's SSVC rates exploitation active
- Would score about 54 if advisories confirm default setups are exposed
What to do
Workaround: The checked facts name no workaround or mitigation. The exposed data is article view passwords, but the facts do not say how to limit that exposure.
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-129493 (Bolo (bolo-solo) 1.7 through 2.6.4 Article Password Disclosure via /articles), 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-129493 (entry last updated 2026-11-16):
Affected:
- bolo-blog bolo-solo: from 1.7, through 2.6.4
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Bolo-solo versions 1.7 through 2.6.4. (source: https://vul.yulun.ac.cn/20261115/bolo-solo/)
- The blog has at least one article with a view password. (source: https://vul.yulun.ac.cn/20261115/bolo-solo/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129493 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129493 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/processor/ArticleProcessor.java#L442-L478
- https://www.vulncheck.com/advisories/bolo-bolo-solo-1.7-through-2.6.4-article-password-disclosure-via-articles
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-129493
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-129493"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- bolo-blog bolo-solo
From 1.7 · through 2.6.4
Evidence 7
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Public exploit code · 1
Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
- Exploit
Other links · 4
- Report
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129493
Is CVE-2026-129493 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The public GET /articles endpoint reveals article view passwords in plaintext to unauthenticated requests. Those passwords can then be used to read password-protected article content.Source: vul.yulun.ac.cn, vulncheck.com
Which versions are affected by CVE-2026-129493?
bolo-solo: from 1.7 through 2.6.4.Source: cve.now feed data
Am I affected, and how do I check?
Bolo-solo versions 1.7 through 2.6.4 are affected, but only on blogs that have at least one article with a view password. To check, look at the installed bolo-solo version and whether any article has a view password set.Source: vul.yulun.ac.cn, vulncheck.com
How do I fix CVE-2026-129493?
The checked facts name no fixed version and no vendor patch IDs, so no upgrade target can be given. Check the vendor's advisory for a fix before relying on any version.Source: vul.yulun.ac.cn, vulncheck.com
What if there's no patch?
The checked facts name no workaround or mitigation. The exposed data is article view passwords, but the facts do not say how to limit that exposure.Source: vul.yulun.ac.cn, vulncheck.com