Wp Event ManagerWordPress extension · Wp Eventmanager
CVE-2023-47697
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in WP Event Manager WP Event Manager – Events Calendar, Registrations, Sell Tickets with WooCommerce plugin <= 3.1.39 versions.
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 confidenceUnauthenticated reflected cross-site scripting (XSS) vulnerability in the WP Event Manager WordPress plugin versions 3.1.39 and below. The vulnerability allows attackers to inject malicious JavaScript through unsanitized user inputs that are reflected back in HTTP responses without proper output encoding.
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
Wp Event ManagerWordPress extension
<= 3.1.39CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed WP Event Manager versionLog in to WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate WP Event Manager, and note the version number displayedAffected if Version listed is 3.1.39 or lower
-
Verify via plugins list page sourceView the plugin page source or check the plugin header in wp-content/plugins/wp-event-manager/ through file browser or FTPAffected if Version in plugin header comments is 3.1.39 or lower
-
Check plugin files for version constantAccess the main plugin file (wp-event-manager.php) via file manager or FTP and locate the version definition in the plugin header commentsAffected if Version defined in the file header is 3.1.39 or lower
If the installed WP Event Manager plugin version is 3.1.39 or lower, the environment is affected by this reflected XSS vulnerability.
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.
dbcve · scopedUpdate WP Event Manager plugin to a version higher than 3.1.39. Until patched, avoid clicking untrusted links and implement WAF rules to filter XSS attack patterns.
Version 3.1.40 or later (latest stable release)
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find WP Event Manager in the plugin list
- Check if an update is available (version higher than 3.1.39)
- If update available, click 'Update Now' to install the patched version
- If no update shows, manually download the latest version from wordpress.org/plugins/wp-event-manager/ and upload via Plugins > Add New > Upload Plugin
- After updating, verify the site functionality remains intact
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Event Manager
Scoped from the published advisory
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47697 — 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-2023-47697 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