CVE-2026-25361
Received Received - Intake
Reflected XSS in WpEvently Plugin Allows Script Injection

Publication date: 2026-03-25

Last updated on: 2026-04-23

Assigner: Patchstack

Description
Improper 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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-25
Last Modified
2026-04-23
Generated
2026-05-07
AI Q&A
2026-03-26
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
magepeopleteam wp_evently to 5.1.4 (inc)
magepeople wp_evently to 5.1.4 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The CVE-2026-25361 vulnerability is a reflected Cross-Site Scripting (XSS) issue that allows attackers to inject malicious scripts into affected websites. This can lead to unauthorized actions or data exposure when visitors interact with the compromised site.

Such unauthorized data exposure and potential compromise of user interactions can negatively impact compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive data against unauthorized access and breaches.

Therefore, if exploited, this vulnerability could result in violations of data protection requirements under these regulations, potentially leading to legal and financial consequences for affected organizations.


Can you explain this vulnerability to me?

CVE-2026-25361 is a medium severity Cross Site Scripting (XSS) vulnerability affecting the WordPress WpEvently plugin versions up to and including 5.1.4.

This vulnerability allows attackers to inject malicious scripts, such as redirects, advertisements, or other HTML payloads, into affected websites.

When visitors access the compromised site, these malicious scripts execute, potentially leading to unauthorized actions or data exposure.

Exploitation requires user interaction by a privileged user, such as clicking a malicious link, visiting a crafted page, or submitting a form, although the initial attack vector can be initiated by an unauthenticated user.

The vulnerability is classified under the OWASP Top 10 category A3: Injection.


How can this vulnerability impact me? :

This vulnerability can lead to unauthorized actions or data exposure on your website.

Attackers can inject malicious scripts that execute when visitors access the compromised site, potentially redirecting users, displaying unwanted advertisements, or stealing sensitive information.

Because the attack can be initiated by an unauthenticated user but requires interaction by a privileged user, it poses a risk of compromising site integrity and user trust.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

The CVE-2026-25361 vulnerability is a reflected Cross Site Scripting (XSS) issue in the WpEvently plugin up to version 5.1.4. Detection typically involves monitoring for suspicious HTTP requests containing malicious script payloads targeting the plugin's input fields.

While no specific commands are provided in the resources, common detection methods include using web application firewalls (WAF) with rules to detect XSS payloads, analyzing web server logs for unusual query parameters or script injections, and employing security scanners that test for reflected XSS vulnerabilities.

For manual inspection, you can use tools like curl or wget to send crafted requests to the affected endpoints and observe if the input is reflected unsanitized in the response, indicating vulnerability.


What immediate steps should I take to mitigate this vulnerability?

The primary immediate mitigation step is to update the WpEvently plugin to version 5.1.5 or later, which contains the patch resolving this XSS vulnerability.

If updating immediately is not possible, applying a mitigation rule provided by Patchstack that blocks attack attempts can help protect the system until the patch is applied.

Additionally, enabling auto-updates for the plugin can ensure rapid protection against this and future vulnerabilities.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart