# CVE-2025-0959: Eventer - WordPress Event & Booking Manager Plugin <= 3.9.9.2 - Authenticated (Subscriber+) SQL Injection via reg_id

> Authenticated attackers with Subscriber access can exploit SQL injection to extract sensitive database information from the Eventer WordPress plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Mar 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-862r-fq3j-wqqx

## What is CVE-2025-0959?

CVE-2025-0959 is a high-severity SQL injection vulnerability in imithemes Eventer - WordPress Event & Booking Manager Plugin, published on 7 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-564 (Use of Hibernate with HQL/SQL Query String Containing External Input)

## Which versions are affected by CVE-2025-0959?

It affects 1 product.


Products: Imithemes Eventer.

## How do I fix CVE-2025-0959?

No fix has been published for CVE-2025-0959 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-0959 being exploited?

There is no known exploitation of CVE-2025-0959 in the wild and no public exploit code.

## Other vulnerabilities in imithemes Eventer - WordPress Event & Booking Manager Plugin

- [CVE-2025-39481](https://insights.sbomify.com/CVE-2025-39481/): WordPress Eventer plugin < 3.11.4 - SQL Injection vulnerability (critical 9.3)
- [CVE-2024-11135](https://insights.sbomify.com/CVE-2024-11135/): Eventer <= 3.9.8 - Unauthenticated SQL Injection via eventer_get_attendees (high 7.5)
- [CVE-2025-22635](https://insights.sbomify.com/CVE-2025-22635/): Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in imithemes Eventer eventer allows Refle (high 7.1)
- [CVE-2024-10799](https://insights.sbomify.com/CVE-2024-10799/): Eventer <= 3.9.7 - Authenticated (Subscriber+) Arbitrary File Read (medium 6.5)
- [CVE-2024-11132](https://insights.sbomify.com/CVE-2024-11132/): Eventer <= 3.9.9.4 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0959 and fix it if it is affected.

What it is: CVE-2025-0959 is a high-severity SQL injection vulnerability in imithemes Eventer - WordPress Event & Booking Manager Plugin, published on 7 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0959 in the wild and no public exploit code.

Affected product: imithemes Eventer - WordPress Event & Booking Manager Plugin. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-0959/ (Markdown: https://insights.sbomify.com/CVE-2025-0959/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-0959
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-0959
- OSV: https://osv.dev/vulnerability/CVE-2025-0959

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-0959/
Summaries are generated and may contain mistakes; the official description above is the record.