Icegram EngageWordPress extension · Icegram
CVE-2016-10962
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe icegram plugin before 1.9.19 for WordPress has CSRF via the wp-admin/edit.php option_name parameter.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe icegram WordPress plugin before version 1.9.19 lacks proper CSRF (Cross-Site Request Forgery) protection on the wp-admin/edit.php page when handling the option_name parameter. This allows attackers to craft malicious requests that trick authenticated administrators into performing unintended actions, such as modifying plugin settings, without the administrator's knowledge.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Icegram EngageWordPress extension
< 1.9.19CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Icegram plugin is installedCheck your WordPress installation's wp-content/plugins directory for the icegram folder, or go to Plugins > Installed Plugins in wp-admin and look for 'Icegram Engage' or 'Icegram' in the list.Affected if The icegram plugin folder exists in wp-content/plugins or appears in the WordPress plugins list.
-
Check installed plugin versionIn wp-admin, go to Plugins > Installed Plugins and locate Icegram. The version number is displayed below the plugin name. Alternatively, open the main plugin file (icegram/icegram.php) and look for the 'Version:' header in the file comments.Affected if The displayed version number is lower than 1.9.19 (for example, 1.9.18, 1.9.10, 1.0, etc).
-
Inspect CSRF protection in edit.php handlingExamine the plugin's PHP files that handle requests on wp-admin/edit.php, specifically code that processes the option_name parameter. Look for presence of wp_verify_nonce, check_admin_referer, or similar nonce validation functions when this parameter is processed.Affected if The code that processes option_name on admin edit.php pages lacks nonce verification calls, meaning the option_name parameter can be modified without a valid anti-CSRF token.
-
Verify admin form submissions lack token validationSearch the plugin source files for form submissions that modify plugin settings. Check if these forms include a hidden nonce field (such as wp_nonce_field) and if the handling code validates it with verify_nonce or check_admin_referer.Affected if Admin-facing forms that modify Icegram settings do not generate or validate CSRF tokens.
You are affected if the Icegram Engage plugin is installed with a version number lower than 1.9.19 and the code handling option_name on wp-admin/edit.php pages lacks nonce validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.9.19
Upgrade the icegram plugin to version 1.9.19 or later which includes proper anti-CSRF token validation for the affected admin forms and parameters.
Fix this in Icegram Engage
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10962 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-10962 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data