CVE-2016-9646 json
Commit metadata forgery via CGI::FormBuilder context-dependent APIs
published 2018-04-13 8 y ago modified 2026-06-17 4 mo ago also EUVD-2016-10447
- cvss
- 5.3
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 66%
- public exploits
- 0
- none known
Summary
ikiwiki before 3.20161229 incorrectly called the CGI::FormBuilder->field method (similar to the CGI->param API that led to Bugzilla's CVE-2014-1572), which can be abused to lead to commit metadata forgery.
Patch / fix
- ikiwiki ikiwiki 3.20161229
- ikiwiki Debian 14, Debian 13, Debian 12 3.20161229
debian advisories DEBIAN-CVE-2016-9646
- ikiwiki openSUSE Tumbleweed 3.20200202.3-2.7
opensuse advisories openSUSE-SU-2024:10860-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2016-9646 updated cvss 5.3
ikiwiki: Commit metadata forgery
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.14% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Affected products
- ikiwiki ikiwiki
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
debian.org
/security/2017/dsa-3760
vendor-advisory, third-party-advisory
-
ikiwiki.info
/security/#cve-2016-9646
vendor-advisory
-
security-tracker.debian.org
/tracker/CVE-2016-9646
issue-tracking, third-party-advisory
-
marc.info
/?l=oss-security&m=148304341511854&w=2
mailing-list, third-party-advisory
Sources
- CVE List CVE-2016-9646
- NVD CVE-2016-9646
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.