AiOPMSD Final 1.0.0 year.php Year sql injection

Summaryinfo

A vulnerability classified as critical has been found in AiOPMSD Final 1.0.0. Affected is an unknown function of the file year.php. Performing a manipulation of the argument Year results in sql injection. This vulnerability was named CVE-2018-25418. The attack may be initiated remotely. In addition, an exploit is available.

Detailsinfo

A vulnerability classified as critical has been found in AiOPMSD Final 1.0.0. This affects some unknown processing of the file year.php. The manipulation of the argument year with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was presented by Ihsan Sencan as 45690. It is possible to read the advisory at exploit-db.com. This vulnerability is uniquely identified as CVE-2018-25418 since 05/30/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:year.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2018-21940). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• AiOPMSD Final

Version

• 1.0.0

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion