# CVE-2025-63007: WordPress EventPrime plugin <= 4.2.4.1 - Sensitive Data Exposure vulnerability

> Attackers can retrieve embedded sensitive data from the EventPrime WordPress plugin, potentially exposing confidential information to unauthorized users.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 9 Dec 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-2x2q-mgpw-ffxm

## What is CVE-2025-63007?

CVE-2025-63007 is a medium-severity vulnerability in Metagauss EventPrime, published on 9 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Insertion of Sensitive Information Into Sent Data vulnerability in Metagauss EventPrime eventprime-event-calendar-management allows Retrieve Embedded Sensitive Data.This issue affects EventPrime: from n/a through <= 4.2.4.1.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

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


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

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

## Is CVE-2025-63007 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63007 is a medium-severity vulnerability in Metagauss EventPrime, published on 9 Dec 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-63007 in the wild and no public exploit code.

Affected product: Metagauss EventPrime. 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-63007/ (Markdown: https://insights.sbomify.com/CVE-2025-63007/index.md)
```

## Sources

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

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