CVE-2026-130872 json
Pytition before 2.10 IDOR Signature Deletion via show_signatures View
published 15h ago modified 14h ago also EUVD-2026-127229
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
Pytition before 2.10 contains an insecure direct object reference vulnerability in the show_signatures view that allows registered users to delete other petitions' signatures by supplying foreign signature IDs. Attackers can post sequential signature IDs to their own petition's signatures page to permanently delete signatures from any user-owned petition and trigger confirmation emails to other signers.
Patch / fix
- Pytition Pytition 2.10
Is CVE-2026-130872 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 7.1 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| CNA | 4.0 | 7.1 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
Affected products
- Pytition Pytition
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
References
-
github.com
/pytition/Pytition/commit/d6301dd6e3774b292fdc04a072b9c9914b9237c3
patch
-
github.com
/pytition/Pytition/issues/347
issue-tracking
-
github.com
/pytition/Pytition/releases/tag/v2.10
release-notes
-
github.com
/pytition/Pytition/blob/v2.9/pytition/petition/views.py#L1424-L1440
technical-description
-
vulncheck.com
/advisories/pytition-before-2.10-idor-signature-deletion-via-show-signatures-view
third-party-advisory
Sources
- CVE List CVE-2026-130872
- NVD CVE-2026-130872
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.