cve.bz

CVE-2022-41927 xwiki xwiki: Cross Site Reference Forgery

7.4 highEPSS 0.4%Fix available

High (7.4) in xwiki xwiki. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in org.xwiki.platform:xwiki-platform-tag-ui 13.10.7, 14.4.1.

On this page
XWiki Platform is vulnerable to Cross-Site Request Forgery (CSRF) that may allow attackers to delete or rename tags without needing any confirmation. The problem has been patched in XWiki 13.10.7, 14.4.1 and 14.5RC1. Workarounds: It's possible to patch existing instances directly by editing the page Main.Tags and add this kind of check, in the code for renaming and for deleting: ``` #if (!$services.csrf.isTokenValid($request.get('form_token'))) #set ($discard = $response.sendError(401, "Wrong CSRF token")) #end ```

Severity

CVSS 3.1

7.4 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N
EPSS
0.4% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 30th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-04-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-352 Cross-Site Request Forgery (Cross Site Reference Forgery)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-41927 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-41927?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-41927?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-41927 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
xwiki:xwikiafter 3.2 before 13.10.7
xwiki:xwiki3.2:milestone2
xwiki:xwiki3.2:milestone3
xwiki:xwiki14.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-mq7h-5574-hw9fMavenorg.xwiki.platform:xwiki-platform-tag-ui>=3.2-milestone-2 <13.10.713.10.7
GHSA-mq7h-5574-hw9fMavenorg.xwiki.platform:xwiki-platform-tag-ui>=14.0.0 <14.4.114.4.1

Attack patterns (CAPEC)

  • CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
  • CAPEC-111 JSON Hijacking (aka JavaScript Hijacking) Likelihood: High · Severity: High
  • CAPEC-462 Cross-Domain Search Timing Severity: Medium
  • CAPEC-467 Cross Site Identification Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON