Remote code execution via unchecked class loading
Published Apr 3, 2025 · Updated Apr 3, 2025
Unsafe reflection in JHipster generator-jhipster-entity-audit before 5.9.1 allows remote authenticated users to execute arbitrary code. In Javers-generated JaversEntityAuditResource.java, entityType and qualifiedName flow into Class.forName without an allowed-class check. Exploitation requires an ADMIN account, access to the audit REST endpoints, and prior placement of a malicious class on the application classpath; loading that class runs its static initializer.
Summary
What happened
Unsafe reflection in JHipster generator-jhipster-entity-audit before 5.9.1 allows remote authenticated users to execute arbitrary code. In Javers-generated JaversEntityAuditResource.java, entityType and qualifiedName flow into Class.forName without an allowed-class check. Exploitation requires an ADMIN account, access to the audit REST endpoints, and prior placement of a malicious class on the application classpath; loading that class runs its static initializer.
The record
- CVE
- CVE-2025-31119
- Published
- Apr 3, 2025
- Updated
- Apr 3, 2025
- Vendor
- JHipster
- Product
- generator-jhipster-entity-audit
- Classifications
- CWE-470
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Apr 3, 2025CVE publishedPublication date reported by the CVE source.
- Apr 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 5.9.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream advisory proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo