CVE-2024-37899: Disabling a user account changes its author, allowing RCE from user account in XWiki
Noroxi assessment
Priority: Monitor (action score 32/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.69% (FIRST EPSS); higher than 53% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: org.xwiki.platform:xwiki-platform-oldcore (Maven) 14.10.21, 15.5.5, 15.10.6.
Low priority for now. Upgrade to org.xwiki.platform:xwiki-platform-oldcore (Maven) 14.10.21, 15.5.5, 15.10.6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. When an admin disables a user account, the user's profile is executed with the admin's rights. This allows a user to place malicious code in the user profile before getting an admin to disable the user account. To reproduce, as a user without script nor programming rights, edit the about section of your user profile and add `{{groovy}}services.logging.getLogger("attacker").error("Hello from Groovy!"){{/groovy}}`. As an admin, go to the user profile and click the "Disable this account" button. Then, reload the page. If the logs show `attacker - Hello from Groovy!` then the instance is vulnerable. This has been patched in XWiki 14.10.21, 15.5.5, 15.10.6 and 16.0.0. Users are advised to upgrade. There are no known workarounds for this vulnerability. ### Workarounds We're not aware of any workaround except upgrading. ### References * https://jira.xwiki.org/browse/XWIKI-21611 * https://github.com/xwiki/xwiki-platform/commit/f89c8f47fad6e5cc7e68c69a7e0acde07f5eed5a
- Published
- Jun 20, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.6% · 53th percentile
- CWE
- CWE-94
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 8.0
- CNA · GitHub_M
- 9.1
- 1.1 point gap
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| xwiki | xwiki | cpe:2.3:a:xwiki:xwiki |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- xwiki xwiki13.10.3 and later · before 14.10.21
- xwiki xwiki15.0 and later · before 15.5.5
- xwiki xwiki15.6 and later · before 15.10.6
- xwiki xwiki13.4.7
- xwiki xwiki13.5
- xwiki xwiki16.0.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
xwiki xwiki-platform
- >= 13.4.7, <= 13.5, >= 13.10.3, < 14.10.21, >= 15.0-rc-1, < 15.5.5, >= 15.6-rc-1, < 15.10.6, >= 16.0.0-rc-1, < 16.0.0affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.xwiki.platform:xwiki-platform-oldcore | from 13.10.3 · before 14.10.21 | 14.10.21 |
| Maven | org.xwiki.platform:xwiki-platform-oldcore | from 13.4.7 · before 14.10.21 | 14.10.21 |
| Maven | org.xwiki.platform:xwiki-platform-oldcore | from 15.0-rc-1 · before 15.5.5 | 15.5.5 |
| Maven | org.xwiki.platform:xwiki-platform-oldcore | from 15.6-rc-1 · before 15.10.6 | 15.10.6 |
| Maven | org.xwiki.platform:xwiki-platform-oldcore | from 16.0.0-rc-1 · before 16.0.0 | 16.0.0 |
Same product
xwiki: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-24893Remote code execution as guest via SolrSearchMacros request in xwikiKEV99Now
- CVE-2024-21650XWiki Remote Code Execution vulnerability via user registration67This week
- CVE-2023-46731Remote code execution through the section parameter in Administration as guest in XWiki Platform66This week
Published before and after this one in the same product
- ← EarlierCVE-2024-31996Apr 10, 2024 · XWiki Commons missing escaping of `{` in Velocity escapetool allows remote code execution40Plan
- ← EarlierCVE-2024-31997Apr 10, 2024 · XWiki Platform remote code execution from account through UIExtension parameters57Plan
- Later →CVE-2024-38369Jun 24, 2024 · XWiki programming rights may be inherited by inclusion17Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.xwiki.platform:xwiki-platform-oldcore | 14.10.21 | Package registry (OSV) |
| Maven:org.xwiki.platform:xwiki-platform-oldcore | 15.10.6 | Package registry (OSV) |
| Maven:org.xwiki.platform:xwiki-platform-oldcore | 15.5.5 | Package registry (OSV) |
| Maven:org.xwiki.platform:xwiki-platform-oldcore | 16.0.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2023-46731227 days apartRemote code execution through the section parameter in Administration as guest in XWiki Platform66This week
- CVE-2023-50721188 days apartXWiki Platform RCE from account through SearchAdmin59Plan
- CVE-2023-37914308 days apartPrivilege escalation (PR)/RCE from account through Invitation subject/message36Monitor
- CVE-2023-50723188 days apartXWiki Platform remote code execution/programming rights with configuration section from any user account35Monitor
- CVE-2023-46242226 days apartCode injection in XWiki Platform35Monitor
- CVE-2023-46243226 days apartCode execution via the edit action in XWiki platform35Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-94 · Improper Control of Generation of Code ('Code Injection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.