How severe is GHSA-cvgc-465m-cw9g?

GHSA-cvgc-465m-cw9g has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-cvgc-465m-cw9g?

GHSA-cvgc-465m-cw9g affects the following packages: org.jeecgframework.boot:jeecg-boot-parent (Maven). Ecosystems affected: Maven.

How do I fix GHSA-cvgc-465m-cw9g?

Update org.jeecgframework.boot:jeecg-boot-parent to 3.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cvgc-465m-cw9g is resolved across your whole dependency graph.

How do I detect GHSA-cvgc-465m-cw9g in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jeecgframework.boot:jeecg-boot-parent. 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.

How do I mitigate GHSA-cvgc-465m-cw9g if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-cvgc-465m-cw9g?

O3 pinpoints whether GHSA-cvgc-465m-cw9g is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-cvgc-465m-cw9g actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-cvgc-465m-cw9g, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What type of vulnerability is GHSA-cvgc-465m-cw9g?

GHSA-cvgc-465m-cw9g is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-cvgc-465m-cw9g published, and has it been updated?

GHSA-cvgc-465m-cw9g was published on June 19, 2023 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-cvgc-465m-cw9g

MEDIUM

GHSA-cvgc-465m-cw9g is a medium-severity (CVSS 6.5) SQL Injection vulnerability in org.jeecgframework.boot:jeecg-boot-parent. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-cvgc-465m-cw9g is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

JeecgBoot vulnerable to SQL injection in queryFilterTableDictInfo

Also known asCVE-2023-34603

Published

Jun 19, 2023

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Blast Radius

1 pkg affected

☕org.jeecgframework.boot:jeecg-boot-parent

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

JeecgBoot up to v 3.5.1 was discovered to contain a SQL injection vulnerability via the component queryFilterTableDictInfo in method org.jeecg.modules.api.controller.SystemApiController.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jeecgframework.boot:jeecg-boot-parent`	all versions	3.5.1

Exploits & PoCs

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

JeecgBoot up to v 3.5.1 was discovered to contain a SQL injection vulner…

github.comNVDJun 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jeecgframework.boot:jeecg-boot-parent. 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.
Fix
Update org.jeecgframework.boot:jeecg-boot-parent to 3.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cvgc-465m-cw9g is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-cvgc-465m-cw9g 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-cvgc-465m-cw9g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

JeecgBoot up to v 3.5.1 was discovered to contain a SQL injection vulnerability via the component `queryFilterTableDictInfo` in method `org.jeecg.modules.api.controller.SystemApiController`.

O3 Security · Impact-Aware SCA

Is GHSA-cvgc-465m-cw9g in your dependencies?

O3 detects GHSA-cvgc-465m-cw9g across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works