# CVE-2025-14370: Quote Comments <= 3.0.0 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Plugin Settings Update

> Authenticated subscribers can arbitrarily update plugin settings due to missing authorization checks in the Quote Comments WordPress plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** 7 Jan 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-rg7p-9gq5-gpcc

## What is CVE-2025-14370?

CVE-2025-14370 is a medium-severity missing authorization vulnerability in metodiew Quote Comments, published on 7 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Quote Comments plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 3.0.0. This is due to missing authorization checks in the quotecomments_add_admin function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update arbitrary plugin options via the 'action' parameter.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-14370 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14370 is a medium-severity missing authorization vulnerability in metodiew Quote Comments, published on 7 Jan 2026. 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-14370 in the wild and no public exploit code.

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

## Sources

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

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