{"answers":{"affected":"1 open source package ship an affected version, including itwanger/paicoding.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-129143 exists.","exposure":"","fix":"No fix has been published for CVE-2026-129143 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-129143 is a high-severity vulnerability in itwanger paicoding, published on 13 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-129143 and fix it if it is affected.\n\nWhat it is: CVE-2026-129143 is a high-severity vulnerability in itwanger paicoding, published on 13 Nov 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-129143 exists.\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-129143/ (Markdown: https://insights.sbomify.com/CVE-2026-129143/index.md)","id":"CVE-2026-129143","markdown":"https://insights.sbomify.com/CVE-2026-129143/index.md","name":"CVE-2026-129143","record":{"aliases":["GHSA-xg9q-98hr-3xwm"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"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.","ecosystems":["GitHub"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"paicoding 1.0.3 Missing Authorization via Article Detail API Endpoint","id":"CVE-2026-129143","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"GitHub","product":null,"products":[],"type":null,"year":"2026"},"n_packages":1,"n_references":4,"n_vendor_status":0,"next":{"headline":"paicoding 1.0.3 Payment Bypass via Guessable Codes in /article/api/pay/callback","id":"CVE-2026-129144"},"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-129143"}],"prev":{"headline":"paicoding commit 766c48b through 903adce Stored XSS via Payment Notifications","id":"CVE-2026-129142"},"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-11-17","vendor_status":[],"vendors":["itwanger"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-129143/"}