Secuno
ENNL
Book demo

CVE-2025-32969

Xwiki SQL injection

9.8 CRITICALEPSS 79.4%
  1. Published23 Apr 2025

Description

XWiki is a generic wiki platform. In versions starting from 1.8 and prior to 15.10.16, 16.4.6, and 16.10.1, it is possible for a remote unauthenticated user to escape from the HQL execution context and perform a blind SQL injection to execute arbitrary SQL statements on the database backend, including when "Prevent unregistered users from viewing pages, regardless of the page rights" and "Prevent unregistered users from editing pages, regardless of the page rights" options are enabled. Depending on the used database backend, the attacker may be able to not only obtain confidential information such as password hashes from the database, but also execute UPDATE/INSERT/DELETE queries. This issue has been patched in versions 16.10.1, 16.4.6 and 15.10.16. There is no known workaround, other than upgrading XWiki.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Xwiki≥ 16.0.0 < 16.4.6 · ≥ 16.5.0 < 16.10.1 · ≥ 1.8 < 15.10.16

Remediation

Fixed in
Xwiki≥ 16.4.6

Frequently asked

Is CVE-2025-32969 being actively exploited?

CVE-2025-32969 is not in the CISA KEV catalog. Its EPSS exploit probability is 79.4%.

How severe is CVE-2025-32969?

CVE-2025-32969 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 79.4% probability of exploitation.

Which products are affected by CVE-2025-32969?

Affected products include Xwiki.

How do I fix CVE-2025-32969?

Upgrade affected software to a fixed version, for example Xwiki 16.4.6 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-32969 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.