CVE
Solo SQL injection in article update API
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/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. b3log Solo version 4.4.0 or earlier Attacker holds an authenticated author account
- 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 an SQL injection vulnerability in the console article update API that allows authenticated authors to inject SQL through unvalidated JSON property names. Attackers can send a PUT request to /console/article/ with crafted property names used as UPDATE column names, then read query results back through the updated article.
Who should check
Teams running b3log Solo 4.4.0 or earlier where authors can log in and use the console article update API.
“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.
b3log Solo version 4.4.0 or earlier Attacker holds an authenticated author accountApply 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-130080 (B3log Solo through 4.4.0 SQL Injection via Article JSON Property Names), 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-130080 (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):
- b3log Solo version 4.4.0 or earlier (source: https://www.vulncheck.com/advisories/b3log-solo-through-4.4.0-sql-injection-via-article-json-property-names)
- Attacker holds an authenticated author account (source: https://www.vulncheck.com/advisories/b3log-solo-through-4.4.0-sql-injection-via-article-json-property-names)
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-130080 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130080 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/console/ArticleConsole.java#L472-L479
- https://github.com/88250/solo/blob/v4.4.0/src/main/java/org/b3log/solo/repository/ArticleRepository.java#L80-L86
- https://www.vulncheck.com/advisories/b3log-solo-through-4.4.0-sql-injection-via-article-json-property-names
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-130080
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-130080"}.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-130080
Is CVE-2026-130080 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?
Solo's article update code builds SQL column names from JSON property names without filtering them. An authenticated author can send crafted JSON property names to inject SQL, then read query results back through the updated article.Source: vulncheck.com
Which versions are affected by CVE-2026-130080?
Solo: through 4.4.0.Source: cve.now feed data
Am I affected, and how do I check?
Solo versions 4.4.0 and earlier are listed as affected, and the attacker needs an authenticated author account. To check your version, look at the Solo release shown in the installed package or the project's version file.Source: vulncheck.com
How do I fix CVE-2026-130080?
No fixed version is listed in the checked facts, so no upgrade target can be named from them. Check the vendor's advisory for a patch or fixed version.Source: vulncheck.com