How severe is CVE-2018-1207?

No CVSS score has been assigned to CVE-2018-1207 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2018-1207?

Affected package information for CVE-2018-1207 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2018-1207?

No fixed release is recorded for CVE-2018-1207 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2018-1207 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2018-1207 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2018-1207 actively exploited in the wild?

Yes. There are 5 known exploit references for CVE-2018-1207, including 1 documented proof-of-concept exploit on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2018-1207?

CVE-2018-1207 has an EPSS (Exploit Prediction Scoring System) score of 90.1%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2018-1207?

CVE-2018-1207 is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2018-1207?

A Nuclei detection template exists for CVE-2018-1207, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2018-1207 published, and has it been updated?

CVE-2018-1207 was published on March 23, 2018 and was last updated on August 5, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2018-1207

CVE-2018-1207 is a Code Injection vulnerability. 5 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

Dell EMC iDRAC7/iDRAC8, versions prior to 2.52.52.52, contain CGI injection vulnerability which could be used to execute remote code. A remote unauthenticated attacker may potentially…

Published

Mar 23, 2018

Updated

Aug 5, 2024

Affected

2 products

Patched

See advisory

Exploits

5 known

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

90.1%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

Dell EMC iDRAC7/iDRAC8, versions prior to 2.52.52.52, contain CGI injection vulnerability which could be used to execute remote code. A remote unauthenticated attacker may potentially be able to use CGI variables to execute remote code.

Affected Products

2 products · 2 configurations

Application

emc idrac7dell

< 2.52.52.52

range

Application

emc idrac8dell

< 2.52.52.52

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-52246remotehardware

Dell EMC iDRAC7/iDRAC8 2.52.52.52 - Remote Code Execution (RCE)

by Photubias · Apr 16, 2025

Exploit-DB Source

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2018-1207 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

How to detect CVE-2018-1207

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2018-1207 -u https://target

Template: Dell iDRAC7/8 Devices - Remote Code Injection
Severity: critical
Impact: Successful exploitation of this vulnerability could allow an attacker to execute arbitrary code on the affected device.
Remediation: Apply the latest firmware updates provided by Dell to mitigate this vulnerability.

Template by ProjectDiscovery nuclei-templates (dwisiswant0), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-1207 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works