How severe is CVE-2009-1850?

CVE-2009-1850 has a CVSS 2.0 base score of 7.5, rated high severity.

Is CVE-2009-1850 being actively exploited?

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

What products are affected by CVE-2009-1850?

CVE-2009-1850 affects Benjamin Curtis Phpbugtracker. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2009-1850?

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

When was CVE-2009-1850 published?

CVE-2009-1850 was published on 2009-06-01 and last updated on 2026-06-16.

CVE-2009-1850

CVE-2009-1850 is a high-severity vulnerability in Benjamin Curtis Phpbugtracker with a CVSS 2.0 base score of 7.5. 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-89.

Key facts

Severity: High (CVSS 2.0 base score 7.5)
EPSS exploit prediction: 1% (58th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-89
Affected product: Benjamin Curtis Phpbugtracker
Published: 2009-06-01
Last modified: 2026-06-16

Description

SQL injection vulnerability in index.php in phpBugTracker 1.0.3 allows remote attackers to execute arbitrary SQL commands via the password parameter.

Frequently asked questions

What is CVE-2009-1850?: SQL injection vulnerability in index.php in phpBugTracker 1.0.3 allows remote attackers to execute arbitrary SQL commands via the password parameter.
How severe is CVE-2009-1850?: CVE-2009-1850 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2009-1850 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (58th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2009-1850?: CVE-2009-1850 affects Benjamin Curtis Phpbugtracker. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2009-1850?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2009-1850 published?: CVE-2009-1850 was published on 2009-06-01 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:benjamin_curtis:phpbugtracker:1.0.3:*:*:*:*:*:*:*

More vulnerabilities in Benjamin Curtis Phpbugtracker

CVE-2009-1851 — High (CVSS 7.5): SQL injection vulnerability in include.php in phpBugTracker 1.0.4 and earlier allows remote attackers to execute…

All CVEs affecting Benjamin Curtis Phpbugtracker →

Other CWE-89 (SQL Injection) vulnerabilities

CVE-2026-54350 — Critical (CVSS 10.0): Budibase is an open-source low-code platform. Prior to 3.39.12, an unauthenticated visitor of any published Budibase…
CVE-2026-8054 — Critical (CVSS 10.0): Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in the Publish Audit API endpoints…
CVE-2026-42287 — Critical (CVSS 10.0): Emlog is an open source website building system. Prior to version 2.6.11, direct SQL injection in article creation and…
CVE-2026-3325 — Critical (CVSS 10.0): SQL injection (SQLi) in MegaCMS v12.0.0, specifically in the “id_territorio” parameter of the…
CVE-2025-10878 — Critical (CVSS 10.0): A SQL injection vulnerability exists in the login functionality of Fikir Odalari AdminPando 1.0.1 before 2026-01-26.…
CVE-2025-57792 — Critical (CVSS 10.0): Explorance Blue versions prior to 8.14.9 contain a SQL injection vulnerability caused by insufficient validation of…

Browse all CWE-89 (SQL Injection) vulnerabilities →