# CVE-2025-0318: Information disclosure in Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin

> Unauthenticated attackers can exfiltrate user metadata from the database due to verbose error messages in the Ultimate Member WordPress plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jan 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-37pw-6vrv-m5h3

## What is CVE-2025-0318?

CVE-2025-0318 is a medium-severity vulnerability in ultimatemember Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin, published on 18 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 2.9.1 through different error messages in the responses. This makes it possible for unauthenticated attackers to exfiltrate data from wp_usermeta table.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Ultimatemember Ultimate Member.

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

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

## Is CVE-2025-0318 being exploited?

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

## Other vulnerabilities in ultimatemember Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin

- [CVE-2020-36155](https://insights.sbomify.com/CVE-2020-36155/): Privilege escalation in n/a (critical 10.0)
- [CVE-2020-36157](https://insights.sbomify.com/CVE-2020-36157/): Privilege escalation in n/a (critical 10.0)
- [CVE-2020-36156](https://insights.sbomify.com/CVE-2020-36156/): Privilege escalation in n/a (critical 9.9)
- [CVE-2024-1071](https://insights.sbomify.com/CVE-2024-1071/): SQL injection in Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin (critical 9.8)
- [CVE-2023-3460](https://insights.sbomify.com/CVE-2023-3460/): Ultimate Member < 2.6.7 - Unauthenticated Privilege Escalation (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0318 is a medium-severity vulnerability in ultimatemember Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin, published on 18 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0318 in the wild and no public exploit code.

Affected product: ultimatemember Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership 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-0318/ (Markdown: https://insights.sbomify.com/CVE-2025-0318/index.md)
```

## Sources

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

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