NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
CRITICAL severity

CVE-2022-28111 — pagehelper

CRITICALFix: pagehelper/Mybatis-PageHelper@554a524

CVE-2022-28111 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in com.github.pagehelper:pagehelper. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for com.github.pagehelper:pagehelper — see the affected versions and patch details below.

MyBatis PageHelper vulnerable to time-blind SQL injection via orderBy parameter

Also known asGHSA-w559-623p-vfg8
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs78th percentile — riskier than 78% of all scored CVEsHighest risk
0.23%0.90%1.57%2.23%0.7%1.7%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
☕com.github.pagehelper:pagehelper

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

MyBatis PageHelper v1.x.x-v3.7.0 v4.0.0-v5.0.0,v5.1.0-v5.3.0 was discovered to contain a time-blind SQL injection vulnerability via the orderBy parameter.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavencom.github.pagehelper:pagehelper≥ 3.5.0&&< 5.3.15.3.1com.github.pagehelper:pagehelper:5.3.1

Affected Products

1 product · 3 configurations
Application
pagehelperpagehelper_project
≥ 5.1.0 && ≤ 5.3.0
range
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

MyBatis PageHelper v1.x.x-v3.7.0 v4.0.0-v5.0.0,v5.1.0-v5.3.0 was discove…

cnblogs.comNVDMay 2022

Report on github.com

github.comNVDDec 2022

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.github.pagehelper:pagehelper, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update com.github.pagehelper:pagehelper to 5.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-28111 is resolved across your whole dependency graph.

  3. Workarounds

    Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

MyBatis PageHelper versions 3.5.x through 5.3.x were discovered to contain a time-blind SQL injection vulnerability via the orderBy parameter.
O3 Security · Impact-Aware SCA

Is CVE-2022-28111 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2022-28111: pagehelper SQL Injection — Fixed in 5.3.1