dbcve.org
Events ManagerWordPress extension · Pixelite

CVE-2015-9297

MEDIUM · 6.1 CVSS v3.1 Published 2019-08-13
Fix available
A fix is available. Upgrade to 5.6 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
The events-manager plugin before 5.6 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 · moderate confidence

Cross-site scripting (XSS) vulnerability in the events-manager WordPress plugin before version 5.6 allows attackers to inject malicious scripts into web pages viewed by other users.

MitigationUpdate the events-manager plugin to version 5.6 or later to patch the XSS vulnerability.

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
Events ManagerWordPress extension
Affected:< 5.6

CVSS 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.1/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify events-manager plugin is installed
    In the WordPress admin dashboard, go to Plugins > Installed Plugins and search for 'Events Manager' or 'events-manager' in the list
    Affected if Plugin appears in the installed plugins list
  2. Check the installed version number
    Find the events-manager entry in the plugins list and note the version number displayed beneath the plugin name, or open wp-content/plugins/events-manager/events-manager.php and locate the Version header comment
    Affected if Version displayed is below 5.6 or cannot be determined
  3. Confirm the plugin is active
    In the plugins list, verify that events-manager shows as 'Active' under the plugin status
    Affected if Plugin is active with a vulnerable version
  4. Identify the product vendor
    Check the plugin description or author field to confirm it is the 'Pixelite Events Manager' plugin (not a similarly named third-party plugin)
    Affected if Plugin is Pixelite Events Manager with version < 5.6

You are affected if the Pixelite Events Manager plugin is installed and active with any version lower than 5.6.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 5.6 or later
Fixed in 5.6
Interim mitigation

Update the events-manager plugin to version 5.6 or later to patch the XSS vulnerability.

Fix this in Events Manager Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-9297 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-9297 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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