# CVE-2025-13091: Shopire <= 1.0.57 - Missing Authorization to Authenticated (Subscriber+) Limited Plugin Install

> Authenticated subscribers can install the fable-extra plugin due to a missing capability check in the Shopire WordPress theme.

- **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-c2c2-q654-5c4f

## What is CVE-2025-13091?

CVE-2025-13091 is a medium-severity missing authorization vulnerability in wpfable Shopire, published on 19 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Shopire theme for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the shopire_admin_install_plugin() function in all versions up to, and including, 1.0.57. This makes it possible for authenticated attackers, with Subscriber-level access and above, to install the 'fable-extra' plugin.

Weakness: CWE-15 (External Control of System or Configuration Setting)

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


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

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

## Is CVE-2025-13091 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13091 is a medium-severity missing authorization vulnerability in wpfable Shopire, 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-13091 in the wild and no public exploit code.

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

## Sources

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

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