Cyber Resilience

CVE-2023-26478

Xwiki 14.3 – 14.4.6

Public PoC
Published
02 March 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 6.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L
EPSS Score 0.0067 49th percentile
Risk Priority 49 floored blend · peak EPSS

Summary

CVE-2023-26478 is a medium-severity Exposed Dangerous Method or Function (CWE-749) vulnerability in Xwiki Xwiki. Its CVSS base score is 6.6 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 49th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

XWiki Platform is a generic wiki platform. Starting in version 14.3-rc-1, `org.xwiki.store.script.TemporaryAttachmentsScriptService#uploadTemporaryAttachment` returns an instance of `com.xpn.xwiki.doc.XWikiAttachment`. This class is not supported to be exposed to users without the `programing` right. `com.xpn.xwiki.api.Attachment` should be used instead and takes case of…

more

checking the user's rights before performing dangerous operations. This has been patched in versions 14.9-rc-1 and 14.4.6. There are no known workarounds for this issue.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-37277Same product: Xwiki Xwiki
CVE-2024-31985Same product: Xwiki Xwiki
CVE-2023-48293Same product: Xwiki Xwiki
CVE-2025-32968Same product: Xwiki Xwiki
CVE-2025-32969Same product: Xwiki Xwiki
CVE-2024-56158Same product: Xwiki Xwiki
CVE-2025-32429Same product: Xwiki Xwiki
CVE-2023-40572Same product: Xwiki Xwiki
CVE-2024-31988Same product: Xwiki Xwiki
CVE-2025-55748Same product: Xwiki Xwiki

Affected Assets

xwiki
xwiki
14.3 — 14.4.6 · 14.5 — 14.9

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 4 hardening rules · 2 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V8.2.1

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-749

Explicitly prohibiting dangerous or unnecessary functions and services prevents exposure of methods that could be directly exploited.

addresses: CWE-749

Minimal functionality removes or avoids exposure of dangerous methods and functions.

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.AA-05 full match
prevents

Enforcing least-privilege authorization directly prevents unrestricted dangerous API methods.

PR.PS-06 mostly match
prevents

Secure SDLC practices stop developers from exposing dangerous functions in the first place.

ID.RA-01 partial match
prevents

Vulnerability identification processes will surface exposed dangerous methods during assessment.

PR.IR-01 partial match
prevents

Logical access controls at the network/environment layer can limit reachability of exposed functions.

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 exposed dangerous functions, but does not prevent their initial introduction.

degrades

Restricting privileged utility programs reduces exposure of dangerous functions, but does not eliminate the underlying weakness.

prevents

Privileged access rights limit who can invoke dangerous methods, but do not address whether the method itself should exist.

prevents

Secure development life cycle requires removal or protection of dangerous APIs during design and coding.

prevents

Application security requirements can mandate that dangerous methods are not exposed in interfaces.

prevents

Secure architecture principles discourage exposing dangerous functions, but do not guarantee their absence.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Ubuntu 22.04 (3 rules)
  • V-260559 Ubuntu 22.04 LTS must ensure only users who need access to security functions are part of sudo group. prevents CWE-749
  • V-260529 Ubuntu 22.04 LTS must be configured so that remote X connections are disabled, unless to fulfill documented and validated mission requirements. prevents CWE-749
  • V-260557 Ubuntu 22.04 LTS must be configured to use AppArmor. prevents CWE-749
Ubuntu 24.04 (1 rule)
  • V-270748 Ubuntu 24.04 LTS must ensure only users who need access to security functions are part of sudo group. prevents CWE-749

References