# CVE-2026-10724: Reviews Feed < 2.6.5 - Unauthenticated Stored Arbitrary Shortcode Execution via Google Reviews

> Unauthenticated attackers can execute arbitrary shortcodes in the Reviews Feed plugin by injecting them into third-party review content.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/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:** 20 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-9cgw-w9ww-cvhp

## What is CVE-2026-10724?

CVE-2026-10724 is a medium-severity code injection vulnerability in Unknown Reviews Feed, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Reviews Feed  WordPress plugin before 2.6.5 does not neutralize WordPress shortcodes contained in third-party review content before rendering it through its dynamic block, allowing unauthenticated attackers to execute arbitrary shortcodes on pages that display the feed by planting a shortcode in a review on the connected source.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-10724?


## How do I fix CVE-2026-10724?

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

## Is CVE-2026-10724 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10724 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10724 and fix it if it is affected.

What it is: CVE-2026-10724 is a medium-severity code injection vulnerability in Unknown Reviews Feed, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10724 exists.

Affected product: Unknown Reviews Feed. 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-2026-10724/ (Markdown: https://insights.sbomify.com/CVE-2026-10724/index.md)
```

## Sources

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

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