CVE-2018-25413
Received Received - Intake
SQL Injection in AiOPMSD Final 1.0.0

Publication date: 2026-05-30

Last updated on: 2026-05-30

Assigner: VulnCheck

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 'q' parameter. Attackers can send GET requests to search.php with crafted SQL payloads to extract sensitive database information including usernames, database names, and version details.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-30
Last Modified
2026-05-30
Generated
2026-05-30
AI Q&A
2026-05-30
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Currently, no data is known.
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
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. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2018-25413 is a high-severity SQL injection vulnerability in AiOPMSD Final 1.0.0, specifically in the 'search.php' file. It allows unauthenticated attackers to inject malicious SQL code through the 'q' parameter in GET requests.

This improper input validation enables attackers to execute arbitrary SQL queries on the backend database without any authentication.

By exploiting this flaw, attackers can extract sensitive information such as database usernames, database names, and version details.


How can this vulnerability impact me? :

This vulnerability can have serious impacts including unauthorized access to sensitive database information.

  • Attackers can retrieve database usernames, database names, and version details.
  • It allows execution of arbitrary SQL commands without authentication, potentially leading to data leakage.
  • The vulnerability can be exploited remotely via crafted GET requests, increasing the risk of data breaches.

How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The SQL injection vulnerability in AiOPMSD Final 1.0.0 allows unauthenticated attackers to extract sensitive database information such as usernames, database names, and version details. This exposure of sensitive data can lead to non-compliance with data protection standards and regulations like GDPR and HIPAA, which require the protection of personal and sensitive information from unauthorized access.

By enabling attackers to access sensitive information without authentication, the vulnerability increases the risk of data breaches, which can result in legal and financial penalties under these regulations.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This SQL injection vulnerability can be detected by sending crafted GET requests to the vulnerable endpoints, especially to search.php with the 'q' parameter containing SQL payloads.

Testing can involve injecting boolean-based blind SQL injection payloads or error-based SQL payloads to observe database responses that reveal sensitive information such as usernames, database names, or version details.

  • Send a GET request to search.php?q=' OR 1=1-- to check for SQL injection.
  • Use tools like curl or wget to automate sending payloads, for example: curl "http://target/search.php?q=' OR 1=1--"
  • Use SQL injection testing tools such as sqlmap targeting the 'q' parameter in search.php to detect and exploit the vulnerability.

What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include disabling or restricting access to the vulnerable search.php endpoint or any other affected PHP files until a patch or fix is applied.

Implement input validation and sanitization on all user-supplied parameters, especially the 'q' parameter, to prevent SQL injection.

Use prepared statements or parameterized queries in the application code to avoid direct insertion of user input into SQL queries.

Monitor web server logs for suspicious GET requests containing SQL injection payloads and block offending IP addresses if necessary.

Apply any available patches or updates from the software vendor or consider upgrading to a secure version if available.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart