Gravity FormsWordPress extension · Mediaburst
CVE-2017-18495
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 gravity-forms-sms-notifications plugin before 2.4.0 for WordPress has XSS.
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 · high confidenceThe gravity-forms-sms-notifications WordPress plugin before version 2.4.0 contains a Cross-Site Scripting (XSS) vulnerability that allows attackers to inject malicious JavaScript code through plugin input fields, potentially compromising user sessions or performing actions on behalf of authenticated users.
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
Gravity FormsWordPress extension
< 2.4.0CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Locate the plugin versionAccess your WordPress admin dashboard and navigate to Plugins > Installed Plugins. Find the entry for 'Mediaburst Gravity Forms' or 'gravity-forms-sms-notifications' and note the version number displayed under the plugin name.Affected if The displayed version number is lower than 2.4.0 (for example, 2.3.0, 2.2.0, 1.x, etc.)
-
Verify the plugin is activeIn the same Plugins screen, confirm that the Mediaburst Gravity Forms plugin shows as 'Active' rather than 'Inactive'.Affected if The plugin is currently active and the version is below 2.4.0
-
Check plugin directory version fileIf you have file system access, navigate to /wp-content/plugins/ and locate the gravity-forms-sms-notifications or mediaburst-gravity-forms-sms folder. Open the main plugin PHP file (often named with -plugin.php or the plugin name) and inspect the 'Version' header in the plugin comment block.Affected if The version header in the plugin file shows a version lower than 2.4.0
-
Confirm the specific plugin nameReview your installed plugins list to confirm the exact name used. Some versions may display as 'Gravity Forms SMS Notifications' by Mediaburst rather than Mediaburst branding.Affected if The plugin exists with a version identifier below 2.4.0 regardless of the exact naming convention used
Your environment is affected if the Mediaburst Gravity Forms SMS Notifications plugin is installed and active at a version lower than 2.4.0.
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 data2.4.0
Update the gravity-forms-sms-notifications plugin to version 2.4.0 or later to apply the security patch that addresses the XSS vulnerability.
Fix this in Gravity Forms
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18495 — 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-2017-18495 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