CVE-2026-25361
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in magepeopleteam WpEvently mage-eventpress allows Reflected XSS.This issue affects WpEvently: from n/a through <= 5.1.4.
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 confidenceReflected XSS vulnerability in the WpEvently WordPress plugin (magepeopleteam) allows attackers to inject malicious scripts into web pages via unsanitized user input that is reflected back in the server's response. The vulnerability affects versions up to and including 5.1.4.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm WpEvently plugin is installedNavigate to wp-content/plugins/ in your WordPress installation and search for a folder named 'wp-evently', 'magepeopleteam', or similar event-related plugin directory. Alternatively, go to WordPress Admin > Plugins and look for 'WpEvently' or 'MagePeople Team' in the installed plugins list.Affected if The plugin folder exists in wp-content/plugins/ or the plugin appears in the WordPress plugins list.
-
Check installed version numberIf the plugin is found, open the main plugin file (usually named wp-evently.php or similar) and locate the version comment in the file header. Alternatively, check the readme.txt file in the plugin folder for the 'Stable tag' version.Affected if The reported version is 5.1.4 or any version 'up to and including 5.1.4'.
-
Verify plugin is activeIn WordPress Admin, go to Plugins > Installed Plugins and confirm whether WpEvently/MagePeople Team is currently activated. An inactive plugin may still pose a risk if activated later.Affected if The plugin shows as 'Active' in the WordPress plugins admin page.
-
Identify user-facing endpointsCheck the plugin's main PHP file for code that handles URL parameters (using $_GET, $_POST, or $_REQUEST) and reflects them back into HTML output without sanitization functions like esc_html(), esc_attr(), or esc_url(). Look for echo or print statements that directly output request parameters.Affected if The plugin code processes user input from URL parameters and echoes it back without proper escaping, using functions like echo $_GET['parameter'] directly in HTML context.
Your environment is affected if the WpEvently plugin is installed, active, and running version 5.1.4 or below, with the vulnerable code that reflects unsanitized user input present in your installation.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate to the latest patched version of WpEvently; until a patch is available, implement proper input validation and output encoding/escaping (using WordPress functions like esc_html(), esc_attr(), and esc_url()) on all user-supplied parameters.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25361 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-25361 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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