Events ManagerWordPress extension · Pixelite
CVE-2013-7478
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 events-manager plugin before 5.5 for WordPress has XSS via EM_Ticket::get_post.
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 confidenceCross-site scripting (XSS) vulnerability in the events-manager WordPress plugin before version 5.5. The vulnerability exists in the EM_Ticket::get_post function, allowing attackers to inject malicious scripts through unsanitized input.
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
< 5.5CVSS 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 Events Manager plugin is installedLog into WordPress admin and navigate to Plugins > Installed Plugins. Look for 'Events Manager' (also known as 'Pixelite Events Manager' or 'Events Manager - Pro') in the list of active plugins.Affected if The plugin appears in the WordPress installation but is not present in the plugins list.
-
Check installed plugin versionIn WordPress admin, find the Events Manager entry in the plugins list. The version number is displayed below the plugin name. Alternatively, inspect the plugin main file (events-manager.php) and look for the 'Version:' header comment.Affected if The displayed version number is less than 5.5 (for example, 5.4.5, 5.4, 5.3.2, etc.).
-
Confirm EM_Ticket class is presentLocate the plugin files in wp-content/plugins/events-manager/ and search for the file containing the EM_Ticket class definition. This is typically in includes/classes/EM_Ticket.php or similar. Verify the get_post method exists within this class.Affected if The EM_Ticket class and get_post method exist in the plugin code, meaning the vulnerable code path is present in the installation.
-
Verify ticket functionality is in useIn the WordPress admin, navigate to Events > Tickets. Check if any tickets have been created for events. The vulnerability in EM_Ticket::get_post affects ticket post data handling.Affected if The site uses the ticket booking feature of Events Manager, allowing user input through ticket forms that would trigger the vulnerable get_post function.
You are affected if the Events Manager plugin is installed with a version lower than 5.5 and the EM_Ticket class with its get_post method is present in the codebase.
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 data5.5
Update the events-manager plugin to version 5.5 or later to patch the XSS vulnerability in EM_Ticket::get_post.
Fix this in Events Manager
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-2013-7478 — 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-2013-7478 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