Events ManagerWordPress extension · Pixelite
CVE-2013-7477
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.2 for WordPress has XSS in the booking form.
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 events-manager WordPress plugin before version 5.5.2 contains a Cross-Site Scripting (XSS) vulnerability in its booking form. Attackers can inject malicious script through the form that executes in the browsers of users who view or submit the compromised booking form.
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.5.2CVSS 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.
-
Confirm Events Manager plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins, or inspect the directory wp-content/plugins/events-manager/ to verify the plugin files exist.Affected if The events-manager plugin is present in the WordPress installation
-
Identify the installed plugin versionIn the WordPress admin, go to Plugins > Installed Plugins and locate the Events Manager plugin to read the version number displayed. Alternatively, open the main plugin file (e.g., events-manager.php) and look for the version header comment.Affected if The version displayed is lower than 5.5.2 (for example, 5.5.1, 5.4, or earlier)
-
Verify booking form functionality is enabledIn the WordPress admin, go to Events > Settings > Booking Options (or similar booking settings page) and confirm that event bookings are enabled for the site.Affected if Bookings are enabled and the booking form can be displayed to users
-
Check if booking forms are publicly accessibleSearch the site pages, posts, or widget areas for the events-manager booking shortcode (such as [event_form] or [em_booking_form]) or check if a booking form page exists that is visible to visitors.Affected if A booking form is published and accessible to anonymous or non-admin users on the site
A site is affected if the Events Manager plugin version is below 5.5.2 AND the booking form feature is enabled and publicly accessible.
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.2
Update the events-manager plugin to version 5.5.2 or later to remediate the XSS vulnerability in the booking form.
Fix this in Events Manager
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-7477 — 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-7477 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