Purei CMS 1.0 events-ajax.php sql injection

Summaryinfo

A vulnerability was found in Purei CMS 1.0 and classified as critical. This vulnerability affects unknown code of the file events-ajax.php. The manipulation results in sql injection. This vulnerability is identified as CVE-2024-58301. The attack can be executed remotely. Additionally, an exploit exists.

Detailsinfo

A vulnerability was found in Purei CMS 1.0. It has been classified as critical. Affected is an unknown code of the file events-ajax.php. The manipulation 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. CVE summarizes:

Purei CMS 1.0 contains a time-based blind SQL injection vulnerability that allows attackers to manipulate database queries through unfiltered user input parameters. Attackers can exploit vulnerable endpoints like getAllParks.php and events-ajax.php by injecting crafted SQL payloads to potentially extract or modify database information.

The weakness was released by Number 7 as 51929. The advisory is shared for download at exploit-db.com. This vulnerability is traded as CVE-2024-58301 since 12/11/2025. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details and a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1505.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:events-ajax.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 Exploit-DB (51929). VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

• Content Management System

Vendor

• Purei

Name

• CMS

Version

• 1.0

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion