Security readout for executives and security teams
Plain-English summary
CVE-2016-10962 is a cross-site request forgery issue in the Icegram WordPress plugin before version 1.9.19. It could let an attacker abuse a logged-in administrator’s browser to submit an unintended request. The public bundle does not describe the business impact or any confirmed exploitation.
Executive priority
Treat this as a targeted hygiene update for WordPress estates, not an emergency based on the supplied evidence. Prioritize internet-facing WordPress sites and any site with multiple administrators or frequent admin browsing.
Technical view
The vulnerability is described as CSRF through the WordPress admin edit.php option_name parameter in Icegram versions before 1.9.19. No CVSS score, CWE, affected CPE, proof of exploitation, or detailed impact is provided in the supplied sources.
Likely exposure
Exposure is limited to WordPress sites that installed Icegram plugin versions older than 1.9.19. Sites without Icegram, or already updated to 1.9.19 or later, are not indicated as affected by the supplied sources.
Exploitation context
The source bundle does not show CISA KEV listing or other evidence of active exploitation. CSRF issues typically depend on a privileged, authenticated user interacting with attacker-controlled content, but the supplied sources do not specify exact impact.
Researcher notes
Evidence is sparse: the CVE record only identifies CSRF in Icegram before 1.9.19 via option_name, with no severity score or detailed impact. Avoid assuming privilege escalation, data loss, or exploitation without additional vendor or advisory confirmation.
Mitigation direction
- Inventory WordPress sites for the Icegram plugin and installed version.
- Update Icegram to version 1.9.19 or a current vendor-supported release.
- Review the WordPress plugin changelog and advisory for vendor-specific guidance.
- If update timing is blocked, assess whether temporarily disabling Icegram is acceptable.
Validation and detection
- Confirm no production site runs Icegram older than 1.9.19.
- Verify updated sites still have expected Icegram functionality.
- Record sites where Icegram is absent to close exposure tracking.
- Monitor vendor and CVE records for any later impact clarification.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2016-10962 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://wordpress.org/plugins/icegram/#developersCVE reference · x_refsource_MISC
- https://sumofpwn.nl/advisory/2016/cross_site_request_forgery_in_icegram_wordpress_plugin.htmlCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.