dbcve.org
EventprimeWordPress extension · Metagauss

CVE-2023-33326

MEDIUM · 6.1 CVSS v3.1 Published 2023-05-28
Fix available
A fix is available. Upgrade to 3.0.0 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 (XSS) Cross-Site Scripting (XSS) vulnerability in EventPrime plugin <= 2.8.6 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 · moderate confidence

An unauthenticated reflected Cross-Site Scripting (XSS) vulnerability exists in the EventPrime WordPress plugin affecting versions up to and including 2.8.6. The vulnerability allows an attacker to inject malicious JavaScript code through a reflected parameter, which executes in the victim's browser when they click a specially crafted link.

MitigationUpdate the EventPrime plugin to the latest version available, which should contain proper input sanitization and output encoding to prevent XSS attacks. If immediate patching is not possible, implement WAF rules to block malicious URL patterns targeting the vulnerable parameter.

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.0.0

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. Identify installed EventPrime version
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, and locate EventPrime to view the version number. Alternatively, use WP-CLI with command 'wp plugin list' or inspect the plugin header in wp-content/plugins/event-prime/event-prime.php
    Affected if Version is 2.8.6 or lower, or any version below 3.0.0
  2. Confirm plugin is active
    Verify the EventPrime plugin is enabled on the site. Check in WordPress admin under Plugins or run 'wp plugin status event-prime' via WP-CLI
    Affected if Plugin is installed and actively installed on the WordPress site
  3. Identify the vulnerable reflected parameter
    Since CVE details specify a reflected parameter but not its name, examine EventPrime public-facing URLs for parameters that accept user input (such as search, id, type, or event parameters). Common vulnerable endpoints include event listings, booking forms, or search functionality
    Affected if The site uses EventPrime with URL parameters that reflect input back to the user without sanitization

You are affected if EventPrime plugin version is below 3.0.0 and the plugin is active on your WordPress site with accessible reflected parameters.

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 3.0.0 or later
Fixed in 3.0.0
Interim mitigation

Update the EventPrime plugin to the latest version available, which should contain proper input sanitization and output encoding to prevent XSS attacks. If immediate patching is not possible, implement WAF rules to block malicious URL patterns targeting the vulnerable parameter.

Recommended fix Moderate confidence

EventPrime version 3.0.0 or later

  1. 1. Log in to the WordPress admin dashboard where the EventPrime plugin is installed.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate the EventPrime plugin in the list.
  4. 4. If an update is available, click 'Update Now' to update to version 3.0.0 or later.
  5. 5. Alternatively, navigate to Plugins > Add New > Upload Plugin to manually upload the version 3.0.0 (or latest) plugin zip file if automatic update is not available.
  6. 6. After updating, verify the plugin is active and functioning correctly.
  7. 7. Clear any caching plugins or server-side caches to ensure the patched version is served.
Caveat Review the EventPrime changelog for version 3.0.0 to check for any breaking changes in functionality or template overrides that may affect your site

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

Fix this in Eventprime Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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