# CVE-2025-14540: Userback <= 1.0.15 - Missing Authorization to Authenticated (Subscriber+) Plugin's Configuration Exposure

> Authenticated subscribers can access sensitive plugin configuration and private content due to missing capability checks in the Userback WordPress plugin.

- **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:** 13 Dec 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-9452-q4cx-rvq7

## What is CVE-2025-14540?

CVE-2025-14540 is a medium-severity missing authorization vulnerability in Userback, published on 13 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Userback plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the userback_get_json function in all versions up to, and including, 1.0.15. This makes it possible for authenticated attackers, with Subscriber-level access and above, to extract plugin's configuration data including the Userback API access token and site's posts/pages contents, including those that have private and draft status.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-14540 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14540 is a medium-severity missing authorization vulnerability in Userback, published on 13 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-14540 in the wild and no public exploit code.

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

## Sources

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

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