# CVE-2026-129144: paicoding 1.0.3 Payment Bypass via Guessable Codes in /article/api/pay/callback


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-cq4w-w6h4-82fx

## What is CVE-2026-129144?

CVE-2026-129144 is a medium-severity vulnerability in itwanger paicoding, published on 13 Nov 2026. 

### Official description

paicoding 1.0.3 contains a payment bypass vulnerability that allows authenticated attackers to unlock paid articles by guessing weak payment confirmation codes. Attackers can start a payment, enumerate roughly 2000 IdUtil.genPayCode counter values, and submit the matching verifyCode to the unauthenticated callback to mark it paid.

Weakness: CWE-334 (Small Space of Random Values)

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

1 open source package ship an affected version, including itwanger/paicoding.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `itwanger/paicoding` | GitHub | `pkg:github/itwanger/paicoding` | From 1.0.3 to 1.0.3 | None |

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

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

## Is CVE-2026-129144 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-129144 is a medium-severity vulnerability in itwanger paicoding, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-129144 in the wild and no public exploit code.

Affected packages and fixed versions:
- itwanger/paicoding (GitHub): affected from 1.0.3 up to 1.0.3; no fix listed

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-129144/ (Markdown: https://insights.sbomify.com/CVE-2026-129144/index.md)
```

## Sources

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

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