dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-13441

HIGH · 7.2 CVSS v3.1 Published 2026-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click 6 weeks old

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
The EventPrime – Events Calendar, Bookings and Tickets plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'new_event_type_background_color' parameter in all versions up to, and including, 4.3.4.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with custom-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires the plugin's Guest Submissions setting (allow_submission_by_anonymous_user) to be enabled, which allows unauthenticated attackers to submit event types via the frontend form; when that setting is disabled, exploitation requires at minimum a subscriber-level authenticated account.

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

The EventPrime WordPress plugin suffers from a stored XSS vulnerability in the 'new_event_type_background_color' parameter due to insufficient input sanitization and output escaping. Attackers with custom-level access (or unauthenticated users if Guest Submissions is enabled) can inject malicious JavaScript that executes whenever users access pages displaying the injected event type background color.

MitigationUpdate the EventPrime plugin to a version beyond 4.3.4.2 when available; alternatively, disable the Guest Submissions setting (allow_submission_by_anonymous_user) and restrict frontend user registration to require administrative approval for accounts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Verify EventPrime plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate EventPrime. Note the installed version number.
    Affected if EventPrime plugin is installed and version is 4.3.4.2 or lower (versions beyond 4.3.4.2 contain the fix)
  2. Check Guest Submissions setting
    Navigate to EventPrime > Settings > General (or look for Guest Submissions/allow_submission_by_anonymous_user setting). Determine if anonymous/submission by anonymous user is enabled.
    Affected if Guest Submissions is enabled, allowing unauthenticated exploitation of this XSS flaw
  3. Identify custom event types with background colors
    Go to EventPrime > Event Types. Review the list for any event types that have a custom background color defined in the color picker/field.
    Affected if Any event type exists with a custom background color value, which is the output field where the XSS would render
  4. Inspect database for injected payload
    Access WordPress database (via phpMyAdmin or CLI). Query the event types table (typically ep_event_types or similar) and look for suspicious HTML/JavaScript in the background_color or new_event_type_background_color field.
    Affected if The background_color field contains unsanitized HTML or script tags, confirming active exploitation

User is affected if EventPrime plugin version is 4.3.4.2 or lower AND either Guest Submissions is enabled (allowing unauthenticated attack) OR a custom-level user account exists with access to create/edit event types, AND event types with custom background colors are displayed on frontend pages.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the EventPrime plugin to a version beyond 4.3.4.2 when available; alternatively, disable the Guest Submissions setting (allow_submission_by_anonymous_user) and restrict frontend user registration to require administrative approval for accounts.

Recommended fix Moderate confidence

EventPrime plugin version 4.3.5 or later

  1. Check the current version of the EventPrime plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. If the installed version is 4.3.4.2 or below, update the plugin to the latest available version
  4. After updating, verify the fix by checking the plugin's changelog for security fixes related to XSS
  5. Consider disabling the Guest Submissions setting (allow_submission_by_anonymous_user) if not needed, as this reduces the attack surface

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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