CVE
paicoding remote access to paid articles via article detail API
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The checked facts name no workaround. Until a fix is available, limiting or blocking unauthenticated access to GET /article/api/data/detail/{articleId} at a gateway or proxy would reduce exposure.
- Published
- 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? →
- 31/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? →
- Unclear
- 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
Paicoding, the product from itwanger, has a missing authorization flaw in its article detail endpoint that lets an unauthenticated attacker read paid, login-only, member-only, and draft articles. The attacker can reach it remotely over the network without logging in by enumerating article IDs through the detail API.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
paicoding 1.0.3 contains a missing authorization vulnerability in the ArticleRestController article detail endpoint that allows unauthenticated attackers to read restricted articles. Attackers can enumerate article IDs via GET /article/api/data/detail/{articleId} to retrieve full content of paid, login-only, member-only and draft articles.
Who should check
Teams running paicoding 1.0.3, the itwanger Java article and forum platform, with its article detail API exposed.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch5/5No patch listed yet
What would change the score
- Would score about 76 if added to CISA KEV
- Would score about 71 if CISA's SSVC rates exploitation active
- Would score about 36 if advisories confirm default setups are exposed
What to do
Workaround: The checked facts name no workaround. Until a fix is available, limiting or blocking unauthenticated access to GET /article/api/data/detail/{articleId} at a gateway or proxy would reduce exposure.
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-129143 (paicoding 1.0.3 Missing Authorization via Article Detail API 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-129143 (entry last updated 2026-11-13):
Affected:
- itwanger paicoding: versions 1.0.3
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Paicoding version 1.0.3 is affected. (source: https://www.vulncheck.com/advisories/paicoding-1.0.3-missing-authorization-via-article-detail-api-endpoint)
- The article detail endpoint GET /article/api/data/detail/{articleId} is reachable and lacks an authorization check. (source: https://www.vulncheck.com/advisories/paicoding-1.0.3-missing-authorization-via-article-detail-api-endpoint)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129143 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129143 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/itwanger/paicoding/issues/137
- https://vul.yulun.ac.cn/20261112/paicoding/
- https://github.com/itwanger/paicoding/blob/903adce70309d340f7eec51ec3c80cfe3c8326c1/paicoding-web/src/main/java/com/github/paicoding/forum/web/front/article/rest/ArticleRestController.java#L87-L94
- https://www.vulncheck.com/advisories/paicoding-1.0.3-missing-authorization-via-article-detail-api-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-129143
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-129143"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- itwanger paicoding
1.0.3
Evidence 6
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 4
- Report
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129143
Is CVE-2026-129143 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?
An unauthenticated attacker can read the full content of paid, login-only, member-only and draft articles. The article detail endpoint GET /article/api/data/detail/{articleId} lacks an authorization check, so attackers can enumerate article IDs to retrieve the content.Source: vulncheck.com
Which versions are affected by CVE-2026-129143?
paicoding: version 1.0.3.Source: cve.now feed data
Am I affected, and how do I check?
Paicoding version 1.0.3 is affected. To check an installation, confirm the paicoding version in use and whether GET /article/api/data/detail/{articleId} responds to requests made without logging in.Source: vulncheck.com
How do I fix CVE-2026-129143?
The checked facts do not name a fixed version or vendor patch for this issue. Check the vendor's advisory or repository for an update that adds an authorization check to the article detail endpoint.Source: vulncheck.com
What if there's no patch?
The checked facts name no workaround. Until a fix is available, limiting or blocking unauthenticated access to GET /article/api/data/detail/{articleId} at a gateway or proxy would reduce exposure.Source: vulncheck.com