CVE-2025-49583VulnerabilityPublished 13 Jun 2025

CVE-2025-49583: xwiki-platform · Privilege Context Switching Error

Affects xwiki-platformSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium : upgrade to 15.10.16 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 15.10.16

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: Low
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Subsequent System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade org.xwiki/xwiki-platform to 15.10.16.

Affected software

Product	Affected	Fixed in
Mavenorg.xwiki/xwiki-platform`pkg:maven/org.xwiki/xwiki-platform`Other threats	Affected <15.10.16	Fixed in 15.10.16

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade all XWiki instances to the patched versions: 15.10.16, 16.4.7, or 16.10.2, depending on the current version branch. 2. For environments where immediate patching is not feasible, restrict document creation permissions to trusted users only, especially limiting the ability to create objects of the class `XWiki.Notifications.Code.NotificationEmailRendererClass`. 3. Implement strict review and approval workflows for any document edits involving Velocity templates or notification-related objects, ensuring that administrators are aware of potential risks before saving changes. 4. Enhance monitoring of outgoing notification emails for unusual patterns, such as unexpected links or mass mailings, to detect potential abuse early. 5. Educate administrators and users about the risks of phishing and the importance of scrutinizing notification content, especially when editing or approving templates. 6. Consider deploying email security solutions with advanced phishing detection and URL filtering to mitigate the impact of any spam or phishing emails generated via this vulnerability. 7. Audit existing documents for the presence of `NotificationEmailRendererClass` objects created by non-privileged users and remove or sanitize them as necessary.

Description

XWiki is a generic wiki platform. When a user without script right creates a document with an `XWiki.Notifications.Code.NotificationEmailRendererClass` object, and later an admin edits and saves that document, the email templates in this object will be used for notifications. No malicious code can be executed, though, as while these templates allow Velocity code, the existing generic analyzer already warns admins before editing Velocity code. The main impact would thus be to send spam, e.g., with phishing links to other users or to hide notifications about other attacks. Note that warnings before editing documents with dangerous properties have only been introduced in XWiki 15.9, before that version, this was a known issue and the advice was simply to be careful. This has been patched in XWiki 16.10.2, 16.4.7 and 15.10.16 by adding an analysis for the respective XClass properties.

Impact

For European organizations using affected versions of XWiki, the vulnerability could lead to increased phishing and spam campaigns originating from legitimate internal systems, potentially undermining trust in internal communications and increasing the risk of credential theft or malware infection. Since the vulnerability does not allow direct code execution or system takeover, the impact on system integrity and availability is limited. However, the ability to manipulate notification emails could be exploited to hide indicators of other attacks or to socially engineer users into unsafe actions. Organizations with large user bases or critical collaboration platforms relying on XWiki are at greater risk of reputational damage and operational disruption due to phishing. Additionally, sectors with stringent regulatory requirements for data protection and communication integrity (e.g., finance, healthcare, government) may face compliance risks if phishing campaigns lead to data breaches. The medium severity and lack of known exploits suggest a moderate but non-negligible threat, especially if attackers combine this vulnerability with other attack vectors.

CWE-270Privilege Context Switching Error (opens in a new tab)
Base weakness
The product does not properly manage privileges while it is switching between different contexts that have different privileges or spheres of control.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
Architecture and Design · Separation of Privilege
Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Using Malicious Files (opens in a new tab)
Hijacking a Privileged Thread of Execution (opens in a new tab)
Leverage Executable Code in Non-Executable Files (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-357Insufficient UI Warning of Dangerous Operations (opens in a new tab)
Base weakness
The user interface provides a warning to a user regarding dangerous or sensitive operations, but the warning is not noticeable enough to warrant attention.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Jun 2025, 17:34 UTC

WeaknessesCWE-270, CWE-357

Technical details

References

Community reviews

Related threats