How severe is CVE-2009-2382?

CVE-2009-2382 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2009-2382 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 6% (93rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2009-2382?

CVE-2009-2382 affects Jay-jayx0r Phpmyblockchecker. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2009-2382?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2009-2382 published?

CVE-2009-2382 was published on 2009-07-08 and last updated on 2026-06-16.

CVE-2009-2382

CVE-2009-2382 is a critical-severity vulnerability in Jay-jayx0r Phpmyblockchecker with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-287.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
CVSS v2: 7.5
EPSS exploit prediction: 6% (93rd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-287
Affected product: Jay-jayx0r Phpmyblockchecker
Published: 2009-07-08
Last modified: 2026-06-16

Description

admin.php in phpMyBlockchecker 1.0.0055 allows remote attackers to bypass authentication and gain administrative access by setting the PHPMYBCAdmin cookie to LOGGEDIN.

Frequently asked questions

What is CVE-2009-2382?: admin.php in phpMyBlockchecker 1.0.0055 allows remote attackers to bypass authentication and gain administrative access by setting the PHPMYBCAdmin cookie to LOGGEDIN.
How severe is CVE-2009-2382?: CVE-2009-2382 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2009-2382 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 6% (93rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2009-2382?: CVE-2009-2382 affects Jay-jayx0r Phpmyblockchecker. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2009-2382?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2009-2382 published?: CVE-2009-2382 was published on 2009-07-08 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:jay-jayx0r:phpmyblockchecker:1.0.0055:*:*:*:*:*:*:*

Other CWE-287 (Improper Authentication) vulnerabilities

CVE-2026-45480 — Critical (CVSS 10.0): Improper authentication in Azure Active Directory allows an unauthorized attacker to elevate privileges over a network.
CVE-2026-46389 — Critical (CVSS 10.0): UDS Identity Config builds the Keycloak configuration image (realm, plugins, theme, truststore, JARs) consumed by UDS…
CVE-2026-10611 — Critical (CVSS 10.0): An authentication bypass vulnerability exists in MISP when LDAP mixed authentication is enabled with OTP enforcement.…
CVE-2026-47280 — Critical (CVSS 10.0): Improper authentication in Azure Resource Manager (ARM) allows an unauthorized attacker to elevate privileges over a…
CVE-2026-42822 — Critical (CVSS 10.0): Improper authentication in Azure Local Disconnected Operations allows an unauthorized attacker to elevate privileges…
CVE-2026-20182 — Critical (CVSS 10.0): May 2026: This security advisory provides the details and fix information for a vulnerability that was discovered and…

Browse all CWE-287 (Improper Authentication) vulnerabilities →