CVE-2026-93872 json
Cotonti 1.0.0 PHP Object Injection via Comments Plugin Edit Action cb Parameter
published 2026-09-18 51 d ago modified 2026-09-24 45 d ago also EUVD-2026-83369
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
Cotonti 1.0.0 passes the base64-decoded cb parameter to unserialize() without allowed_classes restriction in the comments plugin EditAction. Registered users with comment write permissions can instantiate arbitrary PHP objects and potentially achieve file write or code execution through gadget chains.
Patch / fix
- github.com/Cotonti/Cotonti#1897 pull request
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 48 d ago
Exploit prediction
0.71% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 7.7 | CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
| CNA | 4.0 | 7.7 | CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/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 |
Affected products
- Cotonti Cotonti
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
github.com
/Cotonti/Cotonti/pull/1897
patch, issue-tracking
-
github.com
/Cotonti/Cotonti/issues/1894
issue-tracking
-
github.com
/Cotonti/Cotonti/blob/1.0.0/plugins/comments/controllers/actions/EditAction.php
technical-description
-
github.com
/Cotonti/Cotonti/blob/1.0.0/system/cache.php
technical-description
-
github.com
/Cotonti/Cotonti
product
-
vulncheck.com
/advisories/cotonti-1.0.0-php-object-injection-via-comments-plugin-edit-action-cb-parameter
third-party-advisory
Sources
- CVE List CVE-2026-93872
- NVD CVE-2026-93872
Fencer Vulns 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.