Awesome SupportWordPress extension · Getawesomesupport
CVE-2015-9317
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 awesome-support plugin before 3.1.7 for WordPress has XSS via custom information messages.
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 awesome-support WordPress plugin before version 3.1.7 contains a Cross-Site Scripting (XSS) vulnerability. The flaw exists in the handling of custom information messages, where user-supplied input is not properly sanitized before being rendered in the browser, allowing attackers to inject malicious JavaScript code.
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
Awesome SupportWordPress extension
< 3.1.7CVSS 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.
-
Verify the awesome-support plugin is installedLog in to WordPress admin and navigate to Plugins > Installed Plugins. Look for 'Awesome Support' or 'Getawesomesupport Awesome Support' in the list of active plugins.Affected if The plugin is not installed or not active, then the vulnerability does not apply.
-
Check the installed plugin versionIn the plugins list, click on the plugin name or view its details to find the version number. Alternatively, check the plugin's main PHP file (typically in wp-content/plugins/awesome-support/) for the 'Version' header in the plugin comment block.Affected if Version is less than 3.1.7, indicating the installation is affected by this vulnerability.
-
Identify if custom information messages feature is in useLook for plugin settings related to custom information messages. This may be found under the plugin's settings menu in WordPress admin (usually under Plugins > Awesome Support > Settings or similar). Check if any custom messages have been configured.Affected if Custom information messages are configured and the plugin version is below 3.1.7, the stored messages may contain unsanitized XSS payloads.
-
Inspect custom information messages for malicious contentAccess the custom information messages configuration area in the plugin settings. Review any existing custom messages for suspicious patterns such as <script> tags, javascript: URIs, or event handlers like onload, onerror, or onclick.Affected if Any custom information message contains JavaScript code or HTML that could execute in a browser, confirming exploitation has occurred.
You are affected if the Awesome Support plugin is installed with a version lower than 3.1.7 and the custom information messages feature is being used, as unsanitized user input can be rendered as executable JavaScript.
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 data3.1.7
Update the awesome-support plugin to version 3.1.7 or later, which includes proper output escaping for custom information messages to prevent XSS attacks.
Fix this in Awesome Support
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9317 — 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-2015-9317 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