CVE-2024-27920 Vulnerability Analysis & Exploit Details

CVE-2024-27920 Vulnerability Summary

CVE-2024-27920: projectdiscovery/nuclei is a fast and customisable vulnerability scanner based on simple YAML based DSL. A significant security oversight was identified in Nuclei v3, involving the execution of unsigned code templates through workflows. This vulnerability specifically affects users utilizing custom workflows, potentially allowing the execution of malicious code on the user's system. This advisory outlines the impacted users, provides details on the security patch, and suggests mitigation strategies. The vulnerability is addressed in Nuclei v3.2.0. Users are strongly recommended to update to this version to mitigate the security risk. Users should refrain from using custom workflows if unable to upgrade immediately. Only trusted, verified workflows should be executed.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.046% (probability of exploit)

EPSS Percentile: 19.98% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 80.02% of others.

CVE-2024-27920 References

External References

• https://docs.projectdiscovery.io/templates/protocols/code
• https://docs.projectdiscovery.io/templates/reference/template-signing
• https://docs.projectdiscovery.io/templates/workflows/overview
• https://github.com/projectdiscovery/nuclei/pull/4822
• https://github.com/projectdiscovery/nuclei/security/advisories/GHSA-w5wx-6g2r-r78q
• https://docs.projectdiscovery.io/templates/protocols/code
• https://docs.projectdiscovery.io/templates/reference/template-signing
• https://docs.projectdiscovery.io/templates/workflows/overview
• https://github.com/projectdiscovery/nuclei/pull/4822
• https://github.com/projectdiscovery/nuclei/security/advisories/GHSA-w5wx-6g2r-r78q

CWE Common Weakness Enumeration

CAPEC Common Attack Pattern Enumeration and Classification

• Command Line Execution through SQL Injection CAPEC-108 An attacker uses standard SQL injection methods to inject data into the command line for execution. This could be done directly through misuse of directives such as MSSQL_xp_cmdshell or indirectly through injection of data into the database that would be interpreted as shell commands. Sometime later, an unscrupulous backend application (or could be part of the functionality of the same application) fetches the injected data stored in the database and uses this data as command line arguments without performing proper validation. The malicious data escapes that data plane by spawning new commands to be executed on the host.
• Command Delimiters CAPEC-15 An attack of this type exploits a programs' vulnerabilities that allows an attacker's commands to be concatenated onto a legitimate command with the intent of targeting other resources such as the file system or database. The system that uses a filter or denylist input validation, as opposed to allowlist validation is vulnerable to an attacker who predicts delimiters (or combinations of delimiters) not present in the filter or denylist. As with other injection attacks, the attacker uses the command delimiter payload as an entry point to tunnel through the application and activate additional attacks through SQL queries, shell commands, network scanning, and so on.
• Exploiting Multiple Input Interpretation Layers CAPEC-43 An attacker supplies the target software with input data that contains sequences of special characters designed to bypass input validation logic. This exploit relies on the target making multiples passes over the input data and processing a "layer" of special characters with each pass. In this manner, the attacker can disguise input that would otherwise be rejected as invalid by concealing it with layers of special/escape characters that are stripped off by subsequent processing steps. The goal is to first discover cases where the input validation layer executes before one or more parsing layers. That is, user input may go through the following logic in an application: <parser1> --> <input validator> --> <parser2>. In such cases, the attacker will need to provide input that will pass through the input validator, but after passing through parser2, will be converted into something that the input validator was supposed to stop.
• Argument Injection CAPEC-6 An attacker changes the behavior or state of a targeted application through injecting data or command syntax through the targets use of non-validated and non-filtered arguments of exposed services or methods.
• OS Command Injection CAPEC-88 In this type of an attack, an adversary injects operating system commands into existing application functions. An application that uses untrusted input to build command strings is vulnerable. An adversary can leverage OS command injection in an application to elevate privileges, execute arbitrary commands and compromise the underlying operating system.

Other 5 Recently Published CVEs Vulnerabilities

• CVE-2025-1308 – A vulnerability exists in PX Backup whereby sensitive information may be logged under specific conditions.
• CVE-2025-48340 – Cross-Site Request Forgery (CSRF) vulnerability in Danny Vink User Profile Meta Manager allows Privilege Escalation.This issue affects User Profile...
• CVE-2025-3223 – Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in GE Vernova WorkstationST on Windows (EGD Configurat...
• CVE-2025-47949 – samlify is a Node.js library for SAML single sign-on. A Signature Wrapping attack has been found in samlify prior to version 2.10.0, allowing an at...
• CVE-2025-47946 – Symfony UX is an initiative and set of libraries to integrate JavaScript tools into applications. Prior to version 2.25.1, rendering `{{ attributes...