dbcve.org
XwikiApplication

CVE-2022-36091

HIGH · 7.5 CVSS v3.1 Published 2022-09-08
Fix available
A fix is available. Upgrade to 13.10.4 / 14.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
XWiki Platform Web Templates are templates for XWiki Platform, a generic wiki platform. Through the suggestion feature, string and list properties of objects the user shouldn't have access to can be accessed in versions prior to 13.10.4 and 14.2. This includes private personal information like email addresses and salted password hashes of registered users but also other information stored in properties of objects. Sensitive configuration fields like passwords for LDAP or SMTP servers could be accessed. By exploiting an additional vulnerability, this issue can even be exploited on private wikis at least for string properties. The issue is patched in version 13.10.4 and 14.2. Password properties are no longer displayed and rights are checked for other properties. A workaround is available. The template file `suggest.vm` can be replaced by a patched version without upgrading or restarting XWiki unless it has been overridden, in which case the overridden template should be patched, too. This might need adjustments for older versions, though.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

XWiki Platform's suggestion feature in versions prior to 13.10.4 and 14.2 allows unauthorized access to sensitive object properties through the suggest.vm template. This includes private user data (email addresses, salted password hashes) and configuration credentials (LDAP/SMTP passwords) that should be restricted by access controls.

MitigationUpgrade to XWiki 13.10.4 or 14.2, or replace the suggest.vm template file with the patched version while ensuring any overridden templates are also updated.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
XwikiApplication
Affected:>= 1.3, < 13.10.4>= 14.0, < 14.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify XWiki version
    Locate the XWiki version information in the administration dashboard under 'About XWiki' or check the version file in the XWiki installation directory (typically in a version.properties or similar file at the installation root)
    Affected if The installed version falls within < 13.10.4 or >= 14.0 and < 14.2 (specifically: 1.3 to 13.10.3, or 14.0 to 14.1)
  2. Confirm suggest.vm template presence
    Locate the suggest.vm template file in the XWiki web templates directory (commonly at /templates/ or within the webapp resources)
    Affected if The file exists in the default templates location and has not been replaced with a patched version
  3. Verify suggest feature is accessible
    Test access to the suggest action endpoint or check if the suggest macro is available in wiki pages (typically accessible via URL patterns containing 'suggest' or 'suggest.vm')
    Affected if The suggest functionality is enabled and reachable without elevated privileges, allowing user-controlled queries to trigger the vulnerable template

You are affected if your XWiki version is 1.3 through 13.10.3 or 14.0 through 14.1 AND the suggest.vm template is present and accessible to unprivileged users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 13.10.4 / 14.2 or later
Fixed in 13.10.414.2
Interim mitigation

Upgrade to XWiki 13.10.4 or 14.2, or replace the suggest.vm template file with the patched version while ensuring any overridden templates are also updated.

Recommended fix High confidence

13.10.4 (for 13.x installations) or 14.2 (for 14.x installations)

  1. 1. Back up your XWiki installation and database before proceeding
  2. 2. Determine your current major version (13.x or 14.x)
  3. 3. If running 13.x version, upgrade to version 13.10.4
  4. 4. If running 14.x version, upgrade to version 14.2
  5. 5. Follow the standard XWiki upgrade procedure for your deployment method
  6. 6. Clear any caches if necessary and restart XWiki services
  7. 7. Verify the upgrade by checking the XWiki version in the administration interface
  8. 8. Test that the suggestion feature works correctly with proper access controls

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Xwiki Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-36091 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-36091 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data