Security readout for executives and security teams
Plain-English summary
PvPGN Stats 2.4.6 has a reported SQL injection issue in the stats page. If that legacy web component is deployed and reachable, an attacker may be able to interfere with database queries. The source bundle does not provide CVSS, a named patch, or evidence of active exploitation.
Executive priority
Prioritize if PvPGN Stats is internet-facing or connected to sensitive account, game, or community data. Otherwise, handle through legacy application inventory and retirement planning because patch evidence is incomplete.
Technical view
CVE-2017-18288 describes SQL injection in PvPGN Stats 2.4.6 in ladder/stats.php through the GET game parameter. The bundle lists no CWE, CVSS vector, CPE, or vendor advisory. KEV status is false, so exploitation should not be assumed from these sources.
Likely exposure
Exposure is likely limited to environments still running PvPGN Stats 2.4.6, particularly public PvPGN statistics or ladder pages. Asset discovery is the main uncertainty because the CVE record lacks structured CPE data.
Exploitation context
The public description identifies the vulnerable file and parameter, but the provided sources do not show active exploitation, KEV listing, or confirmed weaponized activity. Treat internet-facing instances as higher risk because SQL injection can affect stored application data.
Researcher notes
The strongest evidence is the CVE description and linked disclosure naming PvPGN Stats 2.4.6 and the affected route parameter. No CVSS, CWE, CPE, fixed version, or exploitation telemetry is present in the supplied bundle.
Mitigation direction
- Inventory any PvPGN Stats deployments and confirm version 2.4.6 exposure.
- Restrict public access to PvPGN Stats until vendor or maintainer guidance is confirmed.
- Review the referenced disclosure and upstream project history for patched code or maintained forks.
- Retire or isolate the component if no supported fixed version is available.
Validation and detection
- Search web roots and deployment records for PvPGN Stats installations.
- Confirm whether ladder/stats.php is reachable from untrusted networks.
- Review application logs for unusual requests to the game parameter.
- Check source code handling of the game parameter for parameterized database queries.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Database behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2017-18288 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://rchase.com/blog/posts/pvpgn-stats-multiple-sql-injection-vulnerabilities/CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.