Skip to content
KitploitKITPLOIT
工具博客
提交
工具博客
提交

黑客、渗透测试和网络安全工具,武装您的安全武器库!

Kitploit 是一个黑客、网络安全和渗透测试工具的目录。发现最新的项目更新,查找漏洞、分析系统、自动化测试并加强你的安全。

··订阅源·联系·隐私·© 2026 Kitploit

工具目录

分类

查看所有分类
Loading categories
CVE-2026-0603 — Hibernate ORM Second-Order SQL Injection | Kitploit
工具/GitHubGitHub/eqstlab/cve-2026-0603
Vulnerability AnalysisExploitationWeb Application ExploitationPenetration TestingLearning & EducationDatabase Security
GitHubeqstlab/cve-2026-0603

CVE-2026-0603

Hibernate ORM Second-Order SQL Injection

查看仓库
111天前尚未审核

最受欢迎

查看全部 →

发现我们社区最常用的工具。

探索所有工具

浏览我们的工具集合

查看所有工具 →
分享
内容在请求的语言中不可用。显示英文版本。

CVE-2026-0603 Hibernate ORM Injection / Second-Order SQL Injection

★ CVE-2026-0603 Hibernate SQL Injection PoC ★

https://github.com/user-attachments/assets/2e7c3a89-e26f-48cd-af0b-8b82d32ce71f


Overview

CVE-2026-0603 is a Second-Order SQL Injection vulnerability in Hibernate ORM, a widely used Java ORM framework.
When a user-supplied string primary key containing a malicious SQL payload is used in a bulk DELETE or UPDATE operation, Hibernate inserts the value directly into the WHERE clause without sanitization, causing unintended mass deletion or modification of database records.


Affected Versions

下载工具
CategoryVersion
VulnerableHibernate ORM 5.2.8 ≤ version ≤ 5.6.15
PatchedNo official patch (5.6.x EOL)

Impact

  • Mass deletion of records across multiple tables
  • Mass modification of records across multiple tables
  • Potential exfiltration of sensitive data from the database

Environment

root@kitploit:~
docker build -t cve-2026-0603-hibernate-vuln .
docker run --rm -it -p 8080:8080 --name hibernate-vuln cve-2026-0603-hibernate-vuln

PoC

After starting the vulnerable environment, follow the steps below to reproduce the attack.

Step 1. Register with a malicious username

root@kitploit:~
username: ' or '1' = '1

Step 2. Trigger update or delete

Click the update or delete button on the registered account.

Step 3. Confirm all user data is affected

Verify that the DELETE or UPDATE query was applied to all rows, not just the registered account. For DELETE, all records across both tables are removed. For UPDATE, all records are modified with the attacker-supplied values.


Mitigation

  • Remove the InlineIdsOrClauseBulkIdStrategy setting from application.yml
  • If InlineIdsOrClauseBulkIdStrategy must be used, apply strict whitelist-based input validation on any user-supplied primary key values to reject SQL control characters

Analysis

  • KR: https://www.skshieldus.com/security-insights/reports/eqst-orm-injection-explained
  • EN: https://www.skshieldus.com/en/report?tab=eqst