CVE-2018-25418
Description
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 year parameter. Attackers can send GET requests to year.php with crafted SQL payloads in the year parameter to extract sensitive database information including usernames, database names, and version details.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
AiOPMSD Final 1.0.0 is vulnerable to unauthenticated SQL injection via the year parameter in year.php, allowing attackers to extract sensitive database information.
Vulnerability
AiOPMSD Final 1.0.0 contains an SQL injection vulnerability in year.php. The application fails to sanitize the year GET parameter, allowing unauthenticated attackers to inject arbitrary SQL queries. This affects version 1.0.0 (build 4, released 2017-09-05) as available from the official SourceForge download [1][2].
Exploitation
An attacker can exploit this vulnerability by sending a crafted GET request to year.php with a malicious payload in the year parameter. No authentication is required, as the vulnerable endpoint is publicly accessible. For example, appending an SQL injection payload such as a single quote (') or a UNION statement can trigger the vulnerability and expose database contents. The attacker only needs network access to the target server [3].
Impact
Successful exploitation allows the attacker to execute arbitrary SQL queries against the underlying MySQL database. This can lead to the extraction of sensitive information, including usernames, database names, and database version details. The compromise impacts the confidentiality of the database and may also affect integrity and availability depending on the SQL commands executed [3].
Mitigation
As of the available references, no official patch has been released for this vulnerability. The vendor stated the final version with no further updates, and the project appears to be abandoned. Users are advised to disable or remove the vulnerable year.php file, implement input validation (e.g., allowlisting expected years), or migrate to an alternative solution. This CVE is not listed on the Known Exploited Vulnerabilities (KEV) catalog [1][2][3].
AI Insight generated on May 30, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
4News mentions
0No linked articles in our index yet.