dbcve.org
Wp Event AggregatorWordPress extension · Xylusthemes

CVE-2025-24700

MEDIUM · 6.1 CVSS v3.1 Published 2025-02-14
Fix available
A fix is available. Upgrade to 1.8.3 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Xylus Themes WP Event Aggregator wp-event-aggregator allows Reflected XSS.This issue affects WP Event Aggregator: from n/a through <= 1.8.2.

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

Reflected XSS vulnerability in WP Event Aggregator plugin where user-supplied input is not properly sanitized before being rendered in web pages, allowing injection of malicious JavaScript through crafted URLs.

MitigationUpdate WP Event Aggregator to the latest version to obtain the security patch. If no patched version is available, disable the plugin or implement WAF rules to block XSS attack patterns until a fix is released.

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
Wp Event AggregatorWordPress extension
Affected:< 1.8.3

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 WP Event Aggregator plugin version
    Access WordPress admin panel, navigate to Plugins > Installed Plugins, find 'WP Event Aggregator' by Xylusthemes, and note the version number displayed. Alternatively, check the plugin's main PHP file (e.g., wp-content/plugins/wp-event-aggregator/wp-event-aggregator.php) for the 'Version' header in the plugin comment block.
    Affected if The displayed version number is lower than 1.8.3 (e.g., 1.8.2, 1.7.0, etc.) or if no version is displayed indicating an older installation.
  2. Verify plugin is active
    In WordPress admin under Plugins > Installed Plugins, confirm the WP Event Aggregator plugin has an 'Active' status under the plugin name.
    Affected if The plugin is installed and active, making the vulnerable code executable.
  3. Identify accessible entry points
    Review page source or use browser developer tools to identify URL parameters used by the plugin (such as search queries, event filters, or pagination parameters in URLs containing '/events/' or '?event=', '?s=', '?paged=').
    Affected if URL parameters from the plugin are visible and accept user input without apparent sanitization in the rendered HTML.
  4. Check for injected script patterns
    Examine browser console for XSS warnings or inspect page HTML source around plugin-rendered content for unescaped user-supplied values (look for <script> tags, javascript: URLs, or event handler attributes like onload, onerror).
    Affected if User input from URL parameters appears directly in HTML output without HTML entity encoding (e.g., ' becomes &amp;).

You are affected if WP Event Aggregator version is below 1.8.3 and the plugin is active, with unescaped user input visible in plugin-generated 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
Upgrade available Upgrade to 1.8.3 or later
Fixed in 1.8.3
Interim mitigation

Update WP Event Aggregator to the latest version to obtain the security patch. If no patched version is available, disable the plugin or implement WAF rules to block XSS attack patterns until a fix is released.

Recommended fix Moderate confidence

1.8.3

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Wp Event Aggregator' in the plugin list
  4. Check if the current version is below 1.8.3
  5. If update available, click 'Update Now' to install version 1.8.3
  6. Alternatively, navigate to Dashboard > Updates and update the plugin from there
  7. Verify the update was successful by checking the plugin version after updating

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

Fix this in Wp Event Aggregator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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