{"answers":{"affected":"1 open source package ship an affected version, including itwanger/paicoding.","exploited":"There is no known exploitation of CVE-2026-129144 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-129144 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-129144 is a medium-severity vulnerability in itwanger paicoding, published on 13 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-129144 and fix it if it is affected.\n\nWhat it is: CVE-2026-129144 is a medium-severity vulnerability in itwanger paicoding, published on 13 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-129144 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- itwanger/paicoding (GitHub): affected from 1.0.3 up to 1.0.3; no fix listed\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-129144/ (Markdown: https://insights.sbomify.com/CVE-2026-129144/index.md)","id":"CVE-2026-129144","markdown":"https://insights.sbomify.com/CVE-2026-129144/index.md","name":"CVE-2026-129144","record":{"aliases":["GHSA-cq4w-w6h4-82fx"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-334","name":"Small Space of Random Values"}],"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.","ecosystems":["GitHub"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"paicoding 1.0.3 Payment Bypass via Guessable Codes in /article/api/pay/callback","id":"CVE-2026-129144","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"GitHub","product":null,"products":[],"type":null,"year":"2026"},"n_packages":1,"n_references":5,"n_vendor_status":0,"next":{"headline":"SurveyKing 1.13.2 Unauthenticated Survey Response Disclosure via Result Lookup","id":"CVE-2026-129151"},"nickname":null,"packages":[{"ecosystem":"GitHub","fixed":[],"introduced":["1.0.3"],"last_affected":["1.0.3"],"name_kind":null,"package":"itwanger/paicoding","purl":"pkg:github/itwanger/paicoding","purl_source":"cna","scope":"upstream","source":"CVE-2026-129144"}],"prev":{"headline":"paicoding 1.0.3 Missing Authorization via Article Detail API Endpoint","id":"CVE-2026-129143"},"products":["paicoding"],"published":"2026-11-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-11-13","vendor_status":[],"vendors":["itwanger"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-129144/"}