Cyber Resilience

CVE-2025-0959

SQLi in Imithemes Eventer ≤ 3.9.9.3

Published
07 March 2025
Modified
13 March 2025
Patch / advisory
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0043 35th percentile
Risk Priority 64 floored blend · peak EPSS

Summary

CVE-2025-0959 is a high-severity SQL Injection: Hibernate (CWE-564) vulnerability in Imithemes Eventer. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 35th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-0959 is a SQL injection vulnerability in the Eventer - WordPress Event & Booking Manager Plugin for WordPress, affecting all versions up to and including 3.9.9.2. The flaw arises from insufficient escaping of the user-supplied reg_id parameter and lack of sufficient preparation in the existing SQL query, allowing injection of malicious SQL code. It is associated with CWE-564 (SQL Injection: Unprepared Statement) and CWE-89 (SQL Injection), and carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), indicating high severity due to network accessibility, low complexity, and significant impacts on confidentiality, integrity, and availability.

Authenticated attackers with Subscriber-level access or higher can exploit this vulnerability by manipulating the reg_id parameter to append additional SQL queries to existing ones. This enables extraction of sensitive information from the database, such as user credentials, event data, or other confidential records stored in the WordPress database.

Mitigation details are available in advisories referenced by Wordfence at https://www.wordfence.com/threat-intel/vulnerabilities/id/bd42c89e-57db-458f-910c-404a5615f280?source=cve and the plugin's CodeCanyon page at https://codecanyon.net/item/eventer-wordpress-event-manager-plugin/20972534, published on 2025-03-07. Security practitioners should review these for patch information and update affected installations beyond version 3.9.9.2.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

The Eventer - WordPress Event & Booking Manager Plugin plugin for WordPress is vulnerable to SQL Injection via the reg_id parameter in all versions up to, and including, 3.9.9.2 due to insufficient escaping on the user supplied parameter and lack…

more

of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-26034Shared CWE-89
CVE-2023-46914Shared CWE-89
CVE-2023-44284Shared CWE-89
CVE-2023-48722Shared CWE-89
CVE-2024-4071Shared CWE-89
CVE-2023-49085Shared CWE-89
CVE-2024-25314Shared CWE-89
CVE-2024-0528Shared CWE-89
CVE-2024-8167Shared CWE-89
CVE-2023-7142Shared CWE-89

Affected Assets

imithemes
eventer
≤ 3.9.9.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V6.2.5

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and static analysis can discover dynamic-query construction flaws before deployment.

Input validation directly stops untrusted data from being concatenated into dynamic Hibernate queries.

Requiring documented secure-development standards and tools reduces use of unsafe dynamic SQL patterns.

Secure engineering principles require parameterized queries or ORM-safe APIs instead of string-built SQL.

System monitoring can identify attempted SQLi exploitation via anomalous queries after the weakness exists.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent dynamic SQL construction from untrusted input.

PR.AT-02 partial match
prevents

Training raises developer awareness of SQLi risks and can reduce introduction likelihood (partial) but removes none of the actual coding flaw's risk by itself since technical neutralization is still required.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect injection flaws but does not prevent them at design time.

prevents

Early warnings and shared best-practice information help organizations apply the latest remediation techniques against SQL-injection vulnerabilities.

prevents

Threat-intelligence feeds that surface new SQL-injection campaigns enable rapid updates to query-construction defenses and detection signatures before exploitation occurs.

prevents

Secure SDLC mandates input validation and ORM usage that reduce dynamic SQL injection risk.

prevents

Application security requirements include secure query construction and ORM parameter binding.

prevents

Secure architecture principles discourage dynamic SQL but do not directly address Hibernate misuse.

References