https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 21:17:21 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-227018 EUVD-2026-227018 https://cve.radiocsirt.org/vuln/euvd-2026-227018 https://cve.radiocsirt.org/vuln/fkie_cve-2025-31119 <p>generator-jhipster-entity-audit is a JHipster module to enable entity audit and audit log page. Prior to 5.9.1, generator-jhipster-entity-audit allows unsafe reflection when having Javers selected as Entity Audit Framework. If an attacker manages to place some malicious classes into the classpath and also has access to these REST interface for calling the mentioned REST endpoints, using these lines of code can lead to unintended remote code execution. This vulnerability is fixed in 5.9.1.</p> <p>generator-jhipster-entity-audit is a JHipster module to enable entity audit and audit log page. Prior to 5.9.1, generator-jhipster-entity-audit allows unsafe reflection when having Javers selected as Entity Audit Framework. If an attacker manages to place some malicious classes into the classpath and also has access to these REST interface for calling the mentioned REST endpoints, using these lines of code can lead to unintended remote code execution. This vulnerability is fixed in 5.9.1.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-31119 https://cve.radiocsirt.org/vuln/ghsa-7rmp-3g9f-cvq8 <p><strong>Affected:</strong> npm: generator-jhipster-entity-audit</p> <p>### Summary CWE-470 (Use of Externally-Controlled Input to Select Classes or Code (&#39;Unsafe Reflection&#39;) when having Javers selected as Entity Audit Framework</p> <p>### Details In the following two occurences, user input directly leads to class loading without checking against e.g. a whitelist of allowed classes. This is also known as CWE-470 https://github.com/jhipster/generator-jhipster-entity-audit/blob/e21e83135d10c77d92203c89cb0b0063914e8fe0/generators/spring-boot-javers/templates/src/main/java/_package_/web/rest/JaversEntityAuditResource.java.ejs#L88 https://github.com/jhipster/generator-jhipster-entity-audit/blob/e21e83135d10c77d92203c89cb0b0063914e8fe0/generators/spring-boot-javers/templates/src/main/java/_package_/web/rest/JaversEntityAuditResource.java.ejs#L124</p> <p>So, if an attacker manages to place some malicious classes into the classpath and also has access to these REST interface for calling the mentioned REST endpoints, using these lines of code can lead to unintended remote code execution.</p> <p>### PoC</p> <p>1. Place an arbitrary class with the right package name (starting with JHIpster applications path name) and make it available in class path 2. Gain access to view entity&#39;s audit changelogs (Role: ADMIN) 3. pass in the malicious class name part as `entityType` (first mentioned part) // `qualifiedName` (second mentioned occurence) 4. class gets loaded and static code blocks in there get executed</p> <p>--&gt; Should be limited to the already existing whitelist of classes (see first…</p> <p><strong>Affected:</strong> npm: generator-jhipster-entity-audit</p> <p>### Summary CWE-470 (Use of Externally-Controlled Input to Select Classes or Code (&#39;Unsafe Reflection&#39;) when having Javers selected as Entity Audit Framework</p> <p>### Details In the following two occurences, user input directly leads to class loading without checking against e.g. a whitelist of allowed classes. This is also known as CWE-470 https://github.com/jhipster/generator-jhipster-entity-audit/blob/e21e83135d10c77d92203c89cb0b0063914e8fe0/generators/spring-boot-javers/templates/src/main/java/_package_/web/rest/JaversEntityAuditResource.java.ejs#L88 https://github.com/jhipster/generator-jhipster-entity-audit/blob/e21e83135d10c77d92203c89cb0b0063914e8fe0/generators/spring-boot-javers/templates/src/main/java/_package_/web/rest/JaversEntityAuditResource.java.ejs#L124</p> <p>So, if an attacker manages to place some malicious classes into the classpath and also has access to these REST interface for calling the mentioned REST endpoints, using these lines of code can lead to unintended remote code execution.</p> <p>### PoC</p> <p>1. Place an arbitrary class with the right package name (starting with JHIpster applications path name) and make it available in class path 2. Gain access to view entity&#39;s audit changelogs (Role: ADMIN) 3. pass in the malicious class name part as `entityType` (first mentioned part) // `qualifiedName` (second mentioned occurence) 4. class gets loaded and static code blocks in there get executed</p> <p>--&gt; Should be limited to the already existing whitelist of classes (see first…</p> https://cve.radiocsirt.org/vuln/ghsa-7rmp-3g9f-cvq8