Is CVE-2025-31119 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-31119 being exploited in the wild.

How severe is CVE-2025-31119?

Low severity, with a CVSS score of 3.1, published 4 April 2025.

Which products and versions are affected?

generator-jhipster-entity-audit (npm) SEMVER:introduced=0,fixed=5.9.1.

Is there a fix for CVE-2025-31119?

Yes. generator-jhipster-entity-audit (npm): upgrade to 5.9.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-31119 attacked?

It is attacked over the network.

Am I affected by CVE-2025-31119?

Check whether you run generator-jhipster-entity-audit (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-31119: generator-jhipster-entity-audit unsafe reflection in Javers audit

CVE-2025-31119 · Severity: low · CVSS 3.1 · Published 2025-04-04

generator-jhipster-entity-audit is a code generator used by JHipster applications to add entity audit logging capabilities. The vulnerability allows an authenticated administrator to trigger remote code execution by specifying malicious class names in audit query parameters, provided an attacker has previously injected malicious classes into the application's classpath. This could result in complete system compromise.

Vendors: npm.

Quick answers

Is CVE-2025-31119 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-31119 being exploited in the wild.
How severe is CVE-2025-31119?: Low severity, with a CVSS score of 3.1, published 4 April 2025.
Which products and versions are affected?: generator-jhipster-entity-audit (npm) SEMVER:introduced=0,fixed=5.9.1.
Is there a fix for CVE-2025-31119?: Yes. generator-jhipster-entity-audit (npm): upgrade to 5.9.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-31119 attacked?: It is attacked over the network.
Am I affected by CVE-2025-31119?: Check whether you run generator-jhipster-entity-audit (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

generator-jhipster-entity-audit (npm): upgrade to 5.9.1 or later
```
npm install generator-jhipster-entity-audit@5.9.1
```

Technical details

The vulnerability is an unsafe reflection flaw (CWE-470) in the Javers entity audit REST endpoints. User-supplied input (entityType and qualifiedName parameters) is passed directly to Class.forName() without whitelist validation to load entity classes. An attacker with ADMIN role who can place malicious classes in the classpath can trigger arbitrary class loading, causing static initializers to execute and achieve remote code execution. The vulnerability affects versions up to 5.9.0 and is fixed in 5.9.1. Exploitation requires both prior classpath manipulation and ADMIN-level access.

Affected products

JHipster generator-jhipster-entity-audit <=5.9.0

Identifiers

CVE-2025-31119
GHSA-7rmp-3g9f-cvq8

Timeline

2025-04-03: disclosed: CVE-2025-31119 published
2025-04-03: patched: Fix available in version 5.9.1

References

https://github.com/jhipster/generator-jhipster-entity-audit/security/advisories/GHSA-7rmp-3g9f-cvq8

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.