# CVE-2026-103519: Code injection in WP Ultimate Review

> Authenticated subscribers can execute arbitrary shortcodes in WP Ultimate Review due to improper validation, potentially leading to code execution.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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:** 3 Oct 2026
- **Updated:** 3 Oct 2026
- **Also known as:** GHSA-98rc-jpvj-4hwx

## What is CVE-2026-103519?

CVE-2026-103519 is a medium-severity code injection vulnerability in roxnor WP Ultimate Review, published on 3 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The The WP Ultimate Review plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 2.4.3. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for authenticated attackers, with subscriber-level access and above, to execute arbitrary shortcodes. The bypass relies on WordPress's own strip_shortcodes() function unwrapping the [[tag]] double-bracket escape to a bare [tag] that survives wp_insert_post storage and fires when the publicly queryable xs_review post type is rendered through the_content.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2026-103519 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103519 is a medium-severity code injection vulnerability in roxnor WP Ultimate Review, published on 3 Oct 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-2026-103519 in the wild and no public exploit code.

Affected product: roxnor WP Ultimate Review. 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-103519/ (Markdown: https://insights.sbomify.com/CVE-2026-103519/index.md)
```

## Sources

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

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