# CVE-2018-25076: Events Extension events.php searchResults sql injection

> SQL injection in BigTree Events Extension allows attackers to manipulate database queries, potentially reading or modifying data.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jan 2023
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9mvr-39qp-5cwp

## What is CVE-2018-25076?

CVE-2018-25076 is a medium-severity SQL injection vulnerability in Events Extension, published on 16 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability classified as critical was found in Events Extension on BigTree. Affected by this vulnerability is the function getRandomFeaturedEventByDate/getUpcomingFeaturedEventsInCategoriesWithSubcategories/recacheEvent/searchResults of the file classes/events.php. The manipulation leads to sql injection. The patch is named 11169e48ab1249109485fdb1e0c9fca3d25ba01d. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-218395.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2018-25076?

It affects 1 product.


Products: Events Project Events.

## How do I fix CVE-2018-25076?

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

## Is CVE-2018-25076 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25076 and fix it if it is affected.

What it is: CVE-2018-25076 is a medium-severity SQL injection vulnerability in Events Extension, published on 16 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-25076 in the wild and no public exploit code.

Affected product: Events Extension. 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-2018-25076/ (Markdown: https://insights.sbomify.com/CVE-2018-25076/index.md)
```

## Sources

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

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