dbcve.org
PhpbugtrackerApplication · Phpbugtracker Project

CVE-2015-2147

CRITICAL · 9.8 CVSS v3.0 Published 2017-10-06
Fix available
A fix is available. Upgrade to after 1.6.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Multiple SQL injection vulnerabilities in Issuetracker phpBugTracker before 1.7.0 allow remote attackers to execute arbitrary SQL commands via unspecified parameters.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Multiple SQL injection vulnerabilities exist in phpBugTracker versions prior to 1.7.0. Attackers can inject arbitrary SQL commands through unspecified input parameters, potentially allowing complete database compromise, data exfiltration, or remote code execution in some configurations.

MitigationUpgrade phpBugTracker to version 1.7.0 or later. If upgrading is not immediately possible, implement input validation and parameterized queries on all user-supplied input, or deploy a WAF as a temporary compensating control.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PhpbugtrackerApplication
Affected:<= 1.6.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate phpBugTracker installation
    Search web server document roots for phpBugTracker files, typically in directories named 'phpbugtracker', 'bugtracker', or at the server root. Look for index.php, config.php, or common phpBugTracker file structures.
    Affected if phpBugTracker is found installed on the system
  2. Find installed version number
    Open version.php, README, CHANGELOG, or the main index.php file in the phpBugTracker directory. Look for a variable like $version, VERSION, or a version string in comments/headers.
    Affected if version cannot be determined or is unclear
  3. Compare version to affected range
    Check if the installed version is 1.6.0 or lower, or any version prior to 1.7.0. Common version strings in phpBugTracker include formats like '1.6', '1.6.0', '1.5', etc.
    Affected if version is 1.6.0 or lower (any version < 1.7.0)
  4. Verify database interaction is enabled
    Confirm the application has an active database configuration by checking config.php or similar for database connection parameters (db_type, db_name, db_user). The SQL injection requires database connectivity to be exploitable.
    Affected if database configuration exists and application connects to a database

If phpBugTracker version 1.6.0 or lower is confirmed, the environment is vulnerable to CVE-2015-2147 SQL injection attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.6.0
Interim mitigation

Upgrade phpBugTracker to version 1.7.0 or later. If upgrading is not immediately possible, implement input validation and parameterized queries on all user-supplied input, or deploy a WAF as a temporary compensating control.

Recommended fix High confidence

phpBugTracker 1.7.0 or later

  1. Backup your current phpBugTracker installation and database before proceeding
  2. Download phpBugTracker version 1.7.0 or later from the official source (SourceForge or project repository)
  3. Extract the new version and replace the existing files on your server
  4. Review and restore any custom configurations from your backup
  5. Update the database schema if the upgrade includes migration scripts
  6. Verify the application functions correctly after the upgrade
  7. Confirm the SQL injection vulnerability is resolved by testing the previously vulnerable parameters

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Phpbugtracker Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-2147 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-2147 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data