Cyber Resilience

CVE-2024-46978

Xwiki 13.2 – 14.10.21

Public PoC
Published
18 September 2024
Modified
07 February 2025
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
EPSS Score 0.0052 41th percentile
Risk Priority 52 floored blend · peak EPSS

Summary

CVE-2024-46978 is a medium-severity Incorrect Use of Privileged APIs (CWE-648) vulnerability in Xwiki Xwiki. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Abuse Elevation Control Mechanism (T1548); ranked at the 41th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. It's possible for any user knowing the ID of a notification filter preference of another user, to enable/disable it or even delete it.…

more

The impact is that the target user might start loosing notifications on some pages because of this. This vulnerability is present in XWiki since 13.2-rc-1. This vulnerability has been patched in XWiki 14.10.21, 15.5.5, 15.10.1, 16.0-rc-1. The patch consists in checking properly the rights of the user before performing any action on the filters. Users are advised to upgrade. It's possible to fix manually the vulnerability by editing the document `XWiki.Notifications.Code.NotificationPreferenceService` to apply the changes performed in commit e8acc9d8e6af7dfbfe70716ded431642ae4a6dd4.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
T1548.001 Setuid and Setgid Privilege Escalation
An adversary may abuse configurations where an application has the setuid or setgid bits set in order to get code running in a different (and possibly more privileged) user’s context.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-29507Same product: Xwiki Xwiki
CVE-2025-49580Same product: Xwiki Xwiki
CVE-2024-21648Same product: Xwiki Xwiki
CVE-2025-49583Same product: Xwiki Xwiki
CVE-2023-34465Same product: Xwiki Xwiki
CVE-2023-26475Same product: Xwiki Xwiki
CVE-2024-43401Same product: Xwiki Xwiki
CVE-2024-31997Same product: Xwiki Xwiki
CVE-2025-32974Same product: Xwiki Xwiki
CVE-2026-33229Same product: Xwiki Xwiki

Affected Assets

xwiki
xwiki
13.2 — 14.10.21 · 15.0 — 15.5.5 · 15.6 — 15.10.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V3.5.2
  • V6.4.6

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover incorrect calls to privileged APIs before deployment.

Enforces authorization checks around privileged operations so that an API requiring elevated rights cannot be reached or misused without proper rights.

Least-privilege assignment directly reduces both the availability of privileged APIs and the blast radius when they are invoked incorrectly.

Security engineering principles include correct use of privileged interfaces and safe invocation patterns that stop the weakness from being introduced.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly enforce correct usage of privileged APIs during development.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect incorrect privileged API calls but does not prevent them at design time.

degrades

Restricting privileged utility programs limits the exposure of privileged APIs to misuse.

degrades

Privileged access rights directly govern the correct use of privileged APIs and reduce misuse.

prevents

Secure development lifecycle includes API usage standards that can prevent incorrect privileged calls.

prevents

Application security requirements can specify correct invocation of privileged APIs.

prevents

Secure architecture principles guide proper privilege separation and API usage.

References