# CVE-2026-130081: B3log Solo through 4.4.0 Article View Password Disclosure via /articles

> Unauthenticated attackers can read article view passwords from B3log Solo's articles API and access protected articles.

- **Severity:** High 8.7 (`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 in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 16 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-3pvm-w72m-hh94

## What is CVE-2026-130081?

CVE-2026-130081 is a high-severity information disclosure vulnerability in b3log Solo, published on 16 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

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

1 open source package ship an affected version, including 88250/solo.

An affected version is exposed as installed. No special setting or call is needed.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `88250/solo` | GitHub | `pkg:github/88250/solo` | All versions to 4.4.0 | None |

## How do I fix CVE-2026-130081?

No fix has been published for CVE-2026-130081 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-130081 being exploited?

There is no known exploitation of CVE-2026-130081 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130081 and fix it if it is affected.

What it is: CVE-2026-130081 is a high-severity information disclosure vulnerability in b3log Solo, published on 16 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-130081 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected packages and fixed versions:
- 88250/solo (GitHub): affected all versions up to 4.4.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130081/ (Markdown: https://insights.sbomify.com/CVE-2026-130081/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130081
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130081
- OSV: https://osv.dev/vulnerability/CVE-2026-130081

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130081/
Summaries are generated and may contain mistakes; the official description above is the record.
