CVE-2024-58287: reNgine 2.2.0 Authenticated Command Injection via Scan Engine Configuration

Published Dec 11, 2025
·
Updated

reNgine 2.2.0 contains a command injection vulnerability in the nmapcmd parameter of scan engine configuration that allows authenticated attackers to execute arbitrary commands. Attackers can modify the nmapcmd parameter with malicious base64-encoded payloads to achieve remote code execution during scan engine configuration.

Affected Software

2 affected components
reNgine
Yogeshojha Rengine=2.2.0

Event History

Dec 11, 2025
CVE Published
via MITRE·09:33 PM
Data Sourced
via MITRE·09:33 PM
DescriptionWeakness
Data Sourced
via NVD·10:15 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-58287?

CVE-2024-58287 is classified as a high severity vulnerability due to its capability for authenticated attackers to execute arbitrary commands.

2

How do I fix CVE-2024-58287?

To fix CVE-2024-58287, apply the latest security patch provided by the reNgine development team for version 2.2.0.

3

What type of attack is associated with CVE-2024-58287?

CVE-2024-58287 is associated with command injection attacks that exploit improper validation of the nmap_cmd parameter.

4

Who is affected by CVE-2024-58287?

CVE-2024-58287 affects authenticated users of reNgine version 2.2.0 who can modify the nmap_cmd parameter.

5

What are the potential impacts of CVE-2024-58287?

The potential impacts of CVE-2024-58287 include unauthorized command execution, leading to data breaches or system compromise.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203