Skip to main content
VulnerabilityPublished

CVE-2026-130080: b3log Solo · SQL Injection

Affects b3log SoloSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High.

Data as of 16 Nov 2026, 22:20 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.07.1
CNA (VulnCheck)CVSS 3.16.5
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
b3logSoloAffected
  • <=4.4.0
Fixed in–
GitHubSolopkg:github/SoloOther threatsAffected
  • <=4.4.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, restrict author privileges and monitor API usage to limit exploitation opportunities.

Description

B3log Solo versions up to 4.4.0 have an SQL injection vulnerability in the console article update API. Authenticated authors can exploit this by sending crafted JSON property names in a PUT request to /console/article/, which are used as SQL UPDATE column names without proper validation. This allows injection of SQL commands and reading of query results through the updated article.

References

Community reviews

Loading reviews…