Zsoft OOP CMS BLOG 1.0 Parameter search.php Search sql injection

Summaryinfo

A vulnerability was found in Zsoft OOP CMS BLOG 1.0. It has been rated as critical. This affects an unknown part of the file search.php of the component Parameter Handler. Performing a manipulation of the argument Search results in sql injection. This vulnerability is identified as CVE-2018-25199. The attack can be initiated remotely. Additionally, an exploit exists.

Detailsinfo

A vulnerability classified as critical has been found in Zsoft OOP CMS BLOG 1.0. This affects an unknown function of the file search.php of the component Parameter Handler. The manipulation of the argument search 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:

OOP CMS BLOG 1.0 contains SQL injection vulnerabilities that allow unauthenticated attackers to execute arbitrary SQL queries by injecting malicious code through multiple parameters. Attackers can inject SQL commands via the search parameter in search.php, pageid parameter in page.php, and id parameter in posts.php to extract database information including table names, schema names, and database credentials.

The weakness was released by Ihsan Sencan as 45799. The advisory is shared at exploit-db.com. This vulnerability is uniquely identified as CVE-2018-25199 since 03/06/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. MITRE ATT&CK project uses the attack technique T1505 for this issue.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:search.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 databases at Exploit-DB (45799) and EUVD (EUVD-2018-21651). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Blog Software

Vendor

• Zsoft

Name

• OOP CMS BLOG

Version

• 1.0

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion