# CVE-2026-110131: ThriveX-Server through 4.0 Missing Authorization via Article Retrieval Endpoints

> Unauthenticated attackers can read unpublished and deleted articles by accessing specific API endpoints without proper authorization checks.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-75r3-hhfq-mmwm

## What is CVE-2026-110131?

CVE-2026-110131 is a medium-severity missing authorization vulnerability in LiuYuYang01 ThriveX-Server, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ThriveX-Server through 4.0 contains a missing authorization vulnerability in the GET /api/article and /api/article/{id} endpoints that allows unauthenticated attackers to read unpublished draft and soft-deleted articles. Attackers can request sequential article ids or supply isDraft=true or isDel=true query parameters to retrieve full titles, descriptions and content of non-public articles.

Weakness: CWE-862 (Missing Authorization)

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


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

No fix has been published for CVE-2026-110131 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-110131 being exploited?

There is no known exploitation of CVE-2026-110131 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-110131 and fix it if it is affected.

What it is: CVE-2026-110131 is a medium-severity missing authorization vulnerability in LiuYuYang01 ThriveX-Server, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-110131 in the wild and no public exploit code.

Affected product: LiuYuYang01 ThriveX-Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-110131/ (Markdown: https://insights.sbomify.com/CVE-2026-110131/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-110131
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-110131
- OSV: https://osv.dev/vulnerability/CVE-2026-110131

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-110131/
Summaries are generated and may contain mistakes; the official description above is the record.
