Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2023-26478

MEDIUM

CVE-2023-26478 is a medium-severity (CVSS 6.6) CWE-749 vulnerability in org.xwiki.platform:xwiki-platform-store-filesystem-oldcore. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2023-26478 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

org.xwiki.platform:xwiki-platform-store-filesystem-oldcore has Exposed Dangerous Method or Function

Also known asGHSA-8692-g6g9-gm5p
Published
Mar 2, 2023
Updated
Aug 5, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known

Blast Radius

2 pkgs affected
org.xwiki.platform:xwiki-platform-store-filesystem-oldcoreorg.xwiki.platform:xwiki-platform-store-filesystem-oldcore

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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 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.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.xwiki.platform:xwiki-platform-store-filesystem-oldcore14.3-rc-1&&< 14.4.614.4.6
Mavenorg.xwiki.platform:xwiki-platform-store-filesystem-oldcore14.5&&< 14.9-rc-114.9-rc-1
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-store-filesystem-oldcore. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.xwiki.platform:xwiki-platform-store-filesystem-oldcore to 14.4.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-26478 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2023-26478 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2023-26478. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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 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.
O3 Security · Impact-Aware SCA

Is CVE-2023-26478 in your dependencies?

O3 detects CVE-2023-26478 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.