Skip to main content
VulnerabilityPublished Updated

CVE-2024-9864: EventPrime (WordPress plugin) · Cross-site Scripting

Affects EventPrime (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Oct 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
metagauss EventPrime – Events Calendar, Bookings and TicketsAffected
  • =0
Fixed in–

AI-suggested

Until an official fix is available, restrict or disable front-end event submissions if possible to reduce exposure. Additionally, apply web application firewall (WAF) rules to detect and block suspicious input patterns related to ticket names. Monitor for updates from the vendor metagauss regarding patches or official mitigations.

Description

The EventPrime – Events Calendar, Bookings and Tickets plugin for WordPress is vulnerable to Stored Cross-Site Scripting via ticket names in all versions up to, and including, 4.0.4.7 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is only exploitable when front-end users can submit new events with tickets.

References

Community reviews

Loading reviews…