HiEventsDev Hi.Events up to 1.7.0 Query Parameter orderBy sort_by sql injection

Summaryinfo

A vulnerability, which was classified as critical, has been found in HiEventsDev Hi.Events up to 1.7.0. Affected by this vulnerability is the function orderBy of the component Query Parameter Handler. The manipulation of the argument sort_by leads to sql injection. This vulnerability is documented as CVE-2026-34455. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in HiEventsDev Hi.Events up to 1.7.0. It has been rated as critical. This issue affects the function orderBy of the component Query Parameter Handler. The manipulation of the argument sort_by with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Hi.Events is an open-source event management and ticket selling platform. From version 0.8.0-beta.1 to before version 1.7.1-beta, multiple repository classes pass the user-supplied sort_by query parameter directly to Eloquent's orderBy() without validation, enabling SQL injection. The application uses PostgreSQL which supports stacked queries. This issue has been patched in version 1.7.1-beta.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-34455 since 03/27/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

Upgrading to version 1.7.1-beta eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 01e1aee28d7249f235fdcca8e3a34e88214dcde9 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• HiEventsDev

Name

• Hi.Events

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7.0

License

• open-source

Website

• Product: https://github.com/HiEventsDev/Hi.Events/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion