Skip to main content
Menu
CVEs

CVE

Solo article view password leak in public articles API

Affects B3log Solo 4.4.0 and earlier, but only for articles encrypted with a view password. The checked facts name no fixed version.

CVE-2026-130081

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

8.7HighCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Not reported

Do first: Apply the patch listed under Evidence.

Published
Last modified
Reference
Last checked
26/100 · provisional
Unclear
None on Exploit-DB, Metasploit or GitHub

Summary

B3log Solo through 4.4.0 contains an information disclosure vulnerability that allows unauthenticated attackers to obtain article view passwords by querying the public GET /articles API. The ArticleProcessor.getArticlesByPage handler leaves the articleViewPwd property in JSON responses, letting attackers read passwords for encrypted articles and access their protected content.

Who should check

Teams running B3log Solo 4.4.0 or earlier that publish view-password protected (encrypted) articles.

“Affecting Solo <= 4.4.0”

vulncheck.com

cve.now Index

26Pcve.now Index 26 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.7/10CVSS 8.7
  • No patch0/5No signal

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active
  • Would score about 31 if advisories confirm default setups are exposed

What to do

  • Apply the patch listed under Evidence.

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-130081 (B3log Solo through 4.4.0 Article View 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-130081 (entry last updated 2026-11-16):
Affected:
- b3log Solo: through 4.4.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Solo version 4.4.0 or earlier (source: https://www.vulncheck.com/advisories/b3log-solo-through-4.4.0-article-view-password-disclosure-via-articles)
- The article must be encrypted with a view password (source: https://www.vulncheck.com/advisories/b3log-solo-through-4.4.0-article-view-password-disclosure-via-articles)
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-130081 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130081 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/88250/solo/commit/46308431d479b61d4ac5cc768474efa140c23cc8
- https://github.com/88250/solo/blob/v4.4.0/src/main/java/org/b3log/solo/processor/ArticleProcessor.java#L348-L369
- https://github.com/88250/solo/blob/v4.4.0/src/main/java/org/b3log/solo/service/DataModelService.java#L785-L813
- https://www.vulncheck.com/advisories/b3log-solo-through-4.4.0-article-view-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-130081
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-130081"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • b3log Solo

    through 4.4.0

Evidence 6

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 4

  1. Patch
  2. Repository
  3. Repository
  4. Link

Corrections

None so far.

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

Questions about CVE-2026-130081

Is CVE-2026-130081 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

What does this mean?

Unauthenticated attackers can read the view passwords of encrypted articles through /articles and use them to access the protected content of those articles.Source: vulncheck.com

Which versions are affected by CVE-2026-130081?

Solo: through 4.4.0.Source: cve.now feed data

Am I affected, and how do I check?

Solo version 4.4.0 or earlier is affected, and only where articles are encrypted with a view password. To check, look at the Solo version you run and whether any articles use a view password.Source: vulncheck.com

How do I fix CVE-2026-130081?

The checked facts name no fixed version, patch, or workaround, so check the B3log Solo project or the vendor's advisory for a fix before relying on any update.Source: vulncheck.com