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

CVE-2026-12924

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable 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 Eventin – Event Calendar, Event Registration, Tickets & Booking (AI Powered) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'etn_faq_content' parameter in all versions up to, and including, 4.1.15 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 Eventin WordPress plugin fails to properly sanitize and escape the 'etn_faq_content' parameter, allowing authenticated users with contributor-level access or higher to inject malicious JavaScript that executes in the browsers of users accessing affected pages.

MitigationUpdate the Eventin plugin to a version beyond 4.1.15 when available, or implement input validation and output escaping on the 'etn_faq_content' parameter until the patch is applied.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 Eventin plugin is installed
    In WordPress admin, navigate to Plugins > Installed Plugins and look for 'Eventin' or 'eventin' in the plugin list. Alternatively, check the wp-content/plugins directory for an 'eventin' folder.
    Affected if The Eventin plugin is present in the WordPress installation
  2. Check installed Eventin version
    In WordPress admin, go to Plugins > Instored Plugins and click on 'View Details' for the Eventin plugin to see the version number. Or check the main plugin file header in wp-content/plugins/eventin/eventin.php for the 'Version' comment.
    Affected if The installed version is 4.1.15 or lower
  3. Identify if FAQ functionality is in use
    Check WordPress pages/posts or Eventin settings for any FAQ content blocks. Look for custom post types or settings pages that reference 'FAQ' or 'etn_faq_content'. Database query: SELECT * FROM wp_posts WHERE post_type LIKE '%etn%' OR post_content LIKE '%etn_faq%';
    Affected if FAQ content created using Eventin is present in the site
  4. Verify user role permissions for FAQ editing
    Go to WordPress Users > Roles or check the Eventin plugin settings to confirm which roles can edit FAQ content. Look for contributor, author, or editor roles having access to Eventin FAQ functionality.
    Affected if Users with contributor-level access or higher can edit FAQ content

The environment is affected if Eventin plugin versions 4.1.15 or lower are installed, the FAQ feature is in use, and users with contributor-level access or higher can edit FAQ content.

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 Eventin plugin to a version beyond 4.1.15 when available, or implement input validation and output escaping on the 'etn_faq_content' parameter until the patch is applied.

Recommended fix Moderate confidence

Eventin plugin version 4.1.16 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Eventin – Event Calendar, Event Registration, Tickets & Booking (AI Powered)' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Verify the update completed successfully
  6. 6. Test that the FAQ functionality works correctly after the update

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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