CVE-2018-25419: AiOPMSD Final 1.0.0 SQL Injection via genre.php
AiOPMSD Final 1.0.0 contains an SQL injection vulnerability that allows unauthenticated attackers to execute arbitrary SQL queries by injecting malicious code through the genre parameter. Attackers can send GET requests to genre.php with crafted SQL payloads in the genre parameter to extract sensitive database information including usernames, database names, and version details.
Security readout for executives and security teams
Plain-English summary
AiOPMSD Final 1.0.0 has an unauthenticated SQL injection flaw in a public PHP route. An attacker who can reach the site may query backend database data, including usernames and database details. The sources do not name a vendor patch or confirm active exploitation.
Executive priority
Treat this as high priority where AiOPMSD is exposed to the internet or stores sensitive user data. Prioritize discovery first, because the affected software is specific and may exist outside standard enterprise inventories.
Technical view
CVE-2018-25419 is CWE-89 SQL injection in AiOPMSD Final 1.0.0 through the genre parameter in genre.php. CVSS 4.0 score is 8.8, with network access, low complexity, no privileges, and no user interaction. Public exploit material is referenced, but KEV is false.
Likely exposure
Exposure is likely limited to organizations still running AiOPMSD Final 1.0.0, especially internet-facing deployments. The product appears niche and SourceForge-hosted, so asset discovery may be harder than for mainstream software.
Exploitation context
ExploitDB is listed as an exploit reference, indicating public exploit information exists. The supplied bundle does not show CISA KEV listing or another cited source confirming active exploitation in the wild.
Researcher notes
The bundle supports SQL injection, unauthenticated network reachability, and public exploit availability. It does not provide a patch version, maintainer statement, KEV status, or evidence of active exploitation, so remediation should be validated against vendor guidance.
Mitigation direction
Identify and remove AiOPMSD Final 1.0.0 if it is no longer required.
Check vendor, SourceForge, and advisory pages for any supported fixed release.
Restrict access to trusted networks until remediation is confirmed.
If maintaining the code, replace unsafe SQL handling with parameterized queries.
Review database accounts for least privilege and rotate exposed credentials if compromise is suspected.
Validation and detection
Inventory web servers for AiOPMSD Final 1.0.0 installations.
Confirm whether genre.php is reachable from untrusted networks.
Review web logs for unusual requests to genre.php.
Check database logs for unexpected reads or account enumeration.
Verify compensating controls block unauthenticated access to the affected route.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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.
cwe · medium confidence lookup
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.