CVE
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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
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
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Attacker must hold a visitor account; OAuth-created visitors receive the B3 key used by the bug. OAuth-created visitors receive their username as their B3 key.
- 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
- 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? →
- 15/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? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Who should check
Anyone running B3log Solo 4.4.0 or earlier, especially sites with OAuth sign-in that creates visitor accounts.
“Affecting Solo <= 4.4.0”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Attacker must hold a visitor account; OAuth-created visitors receive the B3 key used by the bug. OAuth-created visitors receive their username as their B3 key.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-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"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- b3log Solo
through 4.4.0
Evidence 6
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 4
- Patch
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130078
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: cve.now feed data
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: vulncheck.com
Which versions are affected by CVE-2026-130078?
Solo: through 4.4.0.Source: cve.now feed data
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: vulncheck.com
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: vulncheck.com