Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2023-36468: Upgrading doesn't prevent exploiting vulnerable XWiki documents

HighCVSS 8.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 36/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: 1.8% (FIRST EPSS); higher than 79.5% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: org.xwiki.platform:xwiki-platform-oldcore (Maven) 15.2-rc-1, 14.10.7; org.xwiki.platform:xwiki-platform-tag-ui (Maven) 14.4, 13.10.6.

Low priority for now. Upgrade to org.xwiki.platform:xwiki-platform-oldcore (Maven) 15.2-rc-1, 14.10.7; org.xwiki.platform:xwiki-platform-tag-ui (Maven) 14.4, 13.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 XWiki installation is upgraded and that upgrade contains a fix for a bug in a document, just a new version of that document is added. In some cases, it's still possible to exploit the vulnerability that was fixed in the new version. The severity of this depends on the fixed vulnerability, for the purpose of this advisory take CVE-2022-36100/GHSA-2g5c-228j-p52x as example - it is easily exploitable with just view rights and critical. When XWiki is upgraded from a version before the fix for it (e.g., 14.3) to a version including the fix (e.g., 14.4), the vulnerability can still be reproduced by adding `rev=1.1` to the URL used in the reproduction steps so remote code execution is possible even after upgrading. Therefore, this affects the confidentiality, integrity and availability of the whole XWiki installation. This vulnerability also affects manually added script macros that contained security vulnerabilities that were later fixed by changing the script macro without deleting the versions with the security vulnerability from the history. This vulnerability doesn't affect freshly installed versions of XWiki. Further, this vulnerability doesn't affect content that is only loaded from the current version of a document like the code of wiki macros or UI extensions. This vulnerability has been patched in XWiki 14.10.7 and 15.2RC1 by forcing old revisions to be executed in a restricted mode that disables all script macros. As a workaround, admins can manually delete old revisions of affected documents. A script could be used to identify all installed documents and delete the history for them. However, also manually added and later corrected code may be affected by this vulnerability so it is easy to miss documents.

Published
Jun 29, 2023
Updated
Jun 17, 2026
EPSS
1.8% · 79th percentile

Report tools

JSON

Action score

36

Monitor

Low priority for now.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 1.8%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
8.8
CNA · GitHub_M
10.0
1.2 point gap

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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.

Follow CVE-2023-36468

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for xwiki records
Is your version affected? Check it

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 help

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

VendorProduct
xwikixwiki

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

    • >= 2.0, < 14.10.7, >= 15.0-rc-1, < 15.2-rc-1affected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • xwiki xwiki2.0 and later · before 14.10.7
  • xwiki xwiki15.0
  • xwiki xwiki15.1

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavenorg.xwiki.platform:xwiki-platform-oldcorefrom 15.0-rc-1 · before 15.2-rc-115.2-rc-1
Mavenorg.xwiki.platform:xwiki-platform-oldcorefrom 2.0 · before 14.10.714.10.7
Mavenorg.xwiki.platform:xwiki-platform-tag-uifrom 14.0 · before 14.414.4
Mavenorg.xwiki.platform:xwiki-platform-tag-uibefore 13.10.613.10.6
Mavenorg.xwiki.platform.applications:xwiki-application-tagfrom 1.7—

Same product

xwiki: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-24893Remote code execution as guest via SolrSearchMacros request in xwikiKEV
    99Now
  • CVE-2024-21650XWiki Remote Code Execution vulnerability via user registration
    67This week
  • CVE-2023-46731Remote code execution through the section parameter in Administration as guest in XWiki Platform
    66This week

Published before and after this one in the same product

  • ← EarlierCVE-2023-35161Jun 23, 2023 · XWiki Platform vulnerable to reflected cross-site scripting via xredirect parameter in DeleteApplication page
    25Monitor
  • ← EarlierCVE-2023-35162Jun 23, 2023 · XPlatform Wiki vulnerable to cross-site scripting via xcontinue parameter in preview actions template
    25Monitor
  • Later →CVE-2023-36469Jun 29, 2023 · Code injection through NotificationRSSService in XWiki Platform
    60This week

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Maven:org.xwiki.platform:xwiki-platform-oldcore14.10.7Package registry (OSV)
Maven:org.xwiki.platform:xwiki-platform-oldcore15.2-rc-1Package registry (OSV)
Maven:org.xwiki.platform:xwiki-platform-tag-ui13.10.6Package registry (OSV)
Maven:org.xwiki.platform:xwiki-platform-tag-ui14.4Package 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.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • 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
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-459 · Incomplete Cleanup

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records