Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven
Not in CISA KEV
HIGH severity

GHSA-79rg-7mv3-jrr5

HIGH

GHSA-79rg-7mv3-jrr5 is a high-severity (CVSS 7.7) SQL Injection vulnerability in org.xwiki.platform:xwiki-platform-ratings-api. 3 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-79rg-7mv3-jrr5 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Rating Script Service expose XWiki to SQL injection

Also known asCVE-2021-21380
Published
Mar 23, 2021
Updated
Mar 13, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
3 known
Exploitation data as of Mar 13, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
org.xwiki.platform:xwiki-platform-ratings-api

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

Impact

This issue impacts only XWiki with the Ratings API installed. The Rating Script Service expose an API to perform SQL requests without escaping the from and where search arguments. This might lead to an SQL script injection quite easily for any user having Script rights on XWiki.

Patches

The problem has been patched in XWiki 12.9RC1.

Workarounds

The only workaround besides upgrading XWiki would be to uninstall the Ratings API in XWiki from the Extension Manager.

References

https://jira.xwiki.org/browse/XWIKI-17662

For more information

If you have any questions or comments about this advisory:

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.xwiki.platform:xwiki-platform-ratings-apiall versions12.9
Exploits & PoCs
3

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-ratings-api. 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-ratings-api to 12.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-79rg-7mv3-jrr5 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 GHSA-79rg-7mv3-jrr5 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 GHSA-79rg-7mv3-jrr5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact This issue impacts only XWiki with the Ratings API installed. The Rating Script Service expose an API to perform SQL requests without escaping the from and where search arguments. This might lead to an SQL script injection quite easily for any user having Script rights on XWiki. ### Patches The problem has been patched in XWiki 12.9RC1. ### Workarounds The only workaround besides upgrading XWiki would be to uninstall the Ratings API in XWiki from the Extension Manager. ### References https://jira.xwiki.org/browse/XWIKI-17662 ### For more information If you have any questions or
O3 Security · Impact-Aware SCA

Is GHSA-79rg-7mv3-jrr5 in your dependencies?

O3 detects GHSA-79rg-7mv3-jrr5 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.