Cross-Site Scripting (XSS) in Issuetracker phpBugTracker (CVE-2015-2144)
Summary
Cross-site scripting in Issuetracker phpBugTracker (CVE-2015-2144). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
Multiple cross-site scripting (XSS) vulnerabilities in Issuetracker phpBugTracker before 1.7.0 allow remote authenticated users to inject arbitrary web script or HTML via the (1) project name parameter to project.php; the (2) use_js parameter to user.php; the (3) use_js parameter to group.php; the (4) Description parameter to status.php; the (5) Description parameter to severity.php; the (6) Regex parameter to os.php; or the (7) Name parameter to database.php.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2015-2144 has been found in Issuetracker phpBugTracker.
Risk of unauthorized operations or information disclosure. CVSS score: 4.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Issuetracker phpBugTracker CVE-2015-2144" on the vendor's site.
CVE-2015-2144 (Issuetracker phpBugTracker) — CWE-79 / CVSS v3 4.8
Attack vector: remote (network-reachable)
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in Issuetracker phpBugTracker.
Check the vendor advisory for the affected versions of Issuetracker phpBugTracker.
Severity: Medium (CVSS 4.8/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Issuetracker phpBugTracker を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory openwall.com
- advisory github.com