Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2022-22881

CRITICAL

SQL Injection in Jeecg-boot

Also known asGHSA-f9pg-g9xw-r5g2
Published
Feb 16, 2022
Updated
Apr 10, 2026
Affected
2 pkgs
Patched
None yet
Exploits
1 known

EPSS Exploitation Probability

via FIRST.org ↗
1.4%probability of exploitation in next 30 days
Lower Risk68th percentile+0.32%
0.53%0.97%1.41%1.85%1.0%1.4%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected
org.jeecgframework.boot:jeecg-boot-baseorg.jeecgframework.boot:jeecg-boot-base-core

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

Jeecg-boot v3.0 was discovered to contain a SQL injection vulnerability via the code parameter in /sys/user/queryUserComponentData.

Affected Packages

2 total
EcosystemPackageVulnerable rangeFix
Mavenorg.jeecgframework.boot:jeecg-boot-baseall versionsNo fix
Mavenorg.jeecgframework.boot:jeecg-boot-base-coreall versionsNo fix
Exploits & PoCs
1

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.jeecgframework.boot:jeecg-boot-base. 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. Remediation status

    No patched version of org.jeecgframework.boot:jeecg-boot-base has shipped for CVE-2022-22881 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    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 CVE-2022-22881 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 CVE-2022-22881. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Jeecg-boot v3.0 was discovered to contain a SQL injection vulnerability via the code parameter in /sys/user/queryUserComponentData.
O3 Security · Impact-Aware SCA

Is CVE-2022-22881 in your dependencies?

O3 detects CVE-2022-22881 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.