dbcve.org
EventprimeWordPress extension · Metagauss

CVE-2023-45637

MEDIUM · 6.1 CVSS v3.1 Published 2023-10-25
Fix available
A fix is available. Upgrade to after 3.1.5 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
Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in EventPrime EventPrime – Events Calendar, Bookings and Tickets plugin <= 3.1.5 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 confidence

An unauthenticated reflected cross-site scripting (XSS) vulnerability exists in the EventPrime WordPress plugin (versions <=3.1.5). The vulnerability allows an attacker to inject malicious JavaScript code through unsanitized input that is reflected in the plugin's HTTP responses, potentially executing in victim browsers when they click crafted malicious links.

MitigationUpgrade to a patched version of EventPrime plugin (version 3.1.6 or higher). Until then, users should avoid clicking untrusted links to sites running this plugin.

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
EventprimeWordPress extension
Affected:<= 3.1.5

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. Locate EventPrime plugin installation
    Check your WordPress installation's wp-content/plugins/ directory for the 'eventprime' folder, or use WP-CLI: wp plugin list --name=eventprime --format=json
    Affected if The eventprime folder does not exist or the plugin is not found in the plugin list
  2. Determine installed EventPrime version
    Check the plugin's main PHP file header for the 'Version' field, or use WP-CLI: wp plugin get eventprime --format=json
    Affected if The version displayed is 3.1.5 or lower (any version <=3.1.5)
  3. Confirm plugin is active
    Use WP-CLI: wp plugin is-active eventprime, or check WordPress admin dashboard Plugins > Installed Plugins page for EventPrime status
    Affected if The plugin shows as active and running on the site
  4. Verify vulnerable endpoint exposure
    Inspect HTTP responses from EventPrime pages (e.g., event listings, booking pages) by using browser dev tools Network tab or curl to check if URL parameters are reflected without sanitization in the response HTML
    Affected if URL parameters appear verbatim in the response HTML without HTML encoding

If EventPrime plugin version is 3.1.5 or lower and the plugin is active, the environment is affected by this reflected XSS vulnerability.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.1.5
Interim mitigation

Upgrade to a patched version of EventPrime plugin (version 3.1.6 or higher). Until then, users should avoid clicking untrusted links to sites running this plugin.

Recommended fix Moderate confidence

Upgrade to the latest available version of EventPrime plugin (version 3.1.6 or later)

  1. Log into the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'EventPrime – Events Calendar, Bookings and Tickets' in the plugin list
  4. Check if the currently installed version is 3.1.5 or below
  5. If vulnerable, click 'Update Now' if an update is available, or download the latest version from the WordPress plugin repository and upload it
  6. After updating, verify the new version number reflects the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Eventprime Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-45637 — 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-2023-45637 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