CVE-2002-1211: Prometheus 6.0 and earlier allows remote attackers to execute arbitrary PHP code via a modified PROMETHEUS_LIB

This month

HIGH 7.5DOWNGRADE

CVE-2002-1211 is a high-severity flaw (CVSS 7.5) affecting prometheus. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Prometheus 6.0 and earlier allows remote attackers to execute arbitrary PHP code via a modified PROMETHEUS_LIBRARY_BASE that points to code stored on a remote server, which is then used in (1) index.php, (2) install.php, or (3) various test_*.php scripts.

Why this priority

High severity
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
EPSS exploit chance	2.8% (top 13%)
CISA exploited list	No
Published	2002-11-12
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: jason orcutt

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2002-11-12 05:00 UTCPublished CVE record published
2026-06-16 21:58 UTCUpdated Record last modified

jason orcutt prometheus DOWNGRADE

Affected: 3.0_beta · 4.0_beta · 6.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.0_beta

1. Check installed version

apt-cache policy prometheus || rpm -q prometheus || prometheus --version

2. No fixed release: DOWNGRADE to a release before 3.0_beta (Debian / Ubuntu)

apt-cache madison prometheus sudo apt install prometheus=<VERSION_BEFORE_3.0_beta> sudo apt-mark hold prometheus

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list prometheus sudo dnf downgrade prometheus-<VERSION_BEFORE_3.0_beta> sudo dnf versionlock add prometheus

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: Jason Orcutt Prometheus 3.0/4.0/6.0 - Remote File Inclusion

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2002-1211?

prometheus: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2002-1211 being exploited?

CVE-2002-1211 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2002-1211 affect?

CVE-2002-1211 affects prometheus. Severity is high (CVSS 7.5). Prometheus 6.0 and earlier allows remote attackers to execute arbitrary PHP code via a modified PROMETHEUS_LIBRARY_BASE that points to code stored on a remote server, which is then used in (1) index.php, (2) install.php, or (3) various test

How urgent is CVE-2002-1211?

Priority 53/100. High severity; Public exploit reference

Software pages

PHP vulnerabilities · Prometheus vulnerabilities

Related CVEs

CVE-2026-42154 HIGH 7.5 UPGRADE Prometheus is an open-source monitoring system and time series database
CVE-2026-42151 HIGH 7.5 UPGRADE Prometheus is an open-source monitoring system and time series database
CVE-2026-44903 MEDIUM 6.1 UPGRADE Prometheus is an open-source monitoring system and time series database
CVE-2026-40179 MEDIUM 6.1 UPGRADE Prometheus is an open-source monitoring system and time series database
CVE-2021-29622 MEDIUM 6.5 UPGRADE Prometheus is an open-source monitoring system and time series database

References

← Back to latest CVEs