---
id: "CVE-2026-130080"
page: "https://infrastack.ai/live/CVE-2026-130080"
kind: "vulnerability"
aliases: ["CVE-2026-130080"]
title: "B3log Solo: SQL injection in article update API lets authors read data"
severity: "high"
cvss: 7.1
epss: null
exploited: false
status: "open"
category: "runtime"
products: [{"name": "B3log Solo", "fixed": [], "affected": "<= 4.4.0", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["b3log-solo", "blog", "java", "runtime", "self-hosted", "sql-injection"]
not_affected_if: ["auth-required", "newer-version", "single-author"]
published_at: "2026-11-16T22:18:23+00:00"
first_seen_at: "2026-11-16T22:39:15+00:00"
updated_at: "2026-11-16T22:41:17+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-130080", "first_seen_at": "2026-11-16T22:39:15+00:00"}, {"source": "analyst", "url": null, "first_seen_at": "2026-11-16T22:41:17+00:00"}]
exploit_sources: []
---

# B3log Solo: SQL injection in article update API lets authors read data

Link for people: https://infrastack.ai/live/CVE-2026-130080 (this .md is for agents)

B3log Solo through 4.4.0 has an SQL injection flaw in its console article update API, where JSON property names are used as UPDATE column names without validation. An authenticated author can send a crafted PUT request to /console/article/ and read query results back through the updated article.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:B3log Solo affected <= 4.4.0 fixed no fixed version listed

## How to check

Solo <= 4.4.0 is affected (version shown in the admin console/footer or the jar/war name). Exposed only if the instance has author accounts you do not fully trust and /console/article/ is reachable. For a source build, check whether your checkout contains commit 46308431d479b61d4ac5cc768474efa140c23cc8 (git merge-base --is-ancestor 46308431d479b61d4ac5cc768474efa140c23cc8 HEAD).

## Fix

No released version carries the fix yet: latest release is v4.4.0 (affected). Fix is in commit 46308431d479b61d4ac5cc768474efa140c23cc8 on 88250/solo master (2026-11-13), which also fixes XSS and B3 sync authorization. Build from master at or after that commit, or wait for the next release. Until then, limit author accounts.

## Timeline

- 2026-11-16T22:39:15+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-130080
- 2026-11-16T22:41:17+00:00 analyst — VulnCheck advisory + maintainer commit 4630843 (2026-11-13, master) read. No release after v4.4.0 (22 Jan) on releases page, so fixed version unknown; fix is commit only. No exploit/PoC seen; social search not done (low-profile).

## Documents

- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/b3log-solo-through-4.4.0-sql-injection-via-article-json-property-names
- [fix] Patch: github.com https://github.com/88250/solo/commit/46308431d479b61d4ac5cc768474efa140c23cc8

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
