# CVE-2025-14342: Missing authorization in SEO Plugin by Squirrly SEO

> Authenticated subscribers can disconnect the site from Squirrly's cloud service due to missing capability checks in the uninstall function.

- **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:** 19 Feb 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-wvrh-v9qh-4m3c

## What is CVE-2025-14342?

CVE-2025-14342 is a medium-severity missing authorization vulnerability in cifi SEO Plugin by Squirrly SEO, published on 19 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The SEO Plugin by Squirrly SEO plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the sq_ajax_uninstall function in all versions up to, and including, 12.4.14. This makes it possible for authenticated attackers, with Subscriber-level access and above, to disconnect the site from Squirrly's cloud service.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-14342 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14342 is a medium-severity missing authorization vulnerability in cifi SEO Plugin by Squirrly SEO, published on 19 Feb 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-14342 in the wild and no public exploit code.

Affected product: cifi SEO Plugin by Squirrly SEO. 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-14342/ (Markdown: https://insights.sbomify.com/CVE-2025-14342/index.md)
```

## Sources

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

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