CVE-2009-1803

NONECVSS 0.0Trending — 3 sources updated this week

0.0

FreePBX 2.5.1, and other 2.4.x, 2.5.x, and pre-release 2.6.x versions, generates different error messages for a failed login attempt depending on whether the user account exists, which allows remote attackers to enumerate valid usernames.

CVSS v3: —
EG Score: 0.0(none)
EPSS: 55.2%
KEV: Not listed

Published

May 28, 2009

Last Modified

April 23, 2026

References (8)

cve@mitrehttp://freepbx.org/trac/ticket/3660
cve@mitrehttp://secunia.com/advisories/34772
cve@mitrehttp://www.osvdb.org/54263
cve@mitrehttp://www.securityfocus.com/bid/34857
af854a3a-2127-422b-91ae-364da2661108http://freepbx.org/trac/ticket/3660
af854a3a-2127-422b-91ae-364da2661108http://secunia.com/advisories/34772
af854a3a-2127-422b-91ae-364da2661108http://www.osvdb.org/54263
af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/34857

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor

Data Freshness Timeline

(refreshed 14× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:10 UTCepss_batch
2026-06-02 20:10 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 00:13 UTCepss_batch
2026-05-31 00:13 UTCepss_batch
2026-05-30 16:44 UTCEG score recompute
2026-05-30 16:44 UTCGHSA enrichment
2026-05-29 13:40 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-26 07:16 UTCepss_batch
2026-05-26 07:16 UTCepss_batch

Frequently asked(4)

What is CVE-2009-1803?

CVE-2009-1803 is a none vulnerability published on May 28, 2009. FreePBX 2.5.1, and other 2.4.x, 2.5.x, and pre-release 2.6.x versions, generates different error messages for a failed login attempt depending on whether the user account exists, which allows remote attackers to enumerate valid usernames.

When was CVE-2009-1803 disclosed?

CVE-2009-1803 was first published in the National Vulnerability Database on May 28, 2009, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2009-1803 actively exploited?

CVE-2009-1803 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 55.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

How do I remediate CVE-2009-1803?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2009-1803, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2009-1803

Explore →

Is Your Infrastructure Affected by CVE-2009-1803?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2009-1803

📅 Published

🔄 Last Modified

🔗 References (8)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(4)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2009-1803?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (8)

Frequently asked(4)

Related CVEs(same CWE)