# CVE-2025-11268: Strong Testimonials <= 3.2.16 - Unauthenticated Arbitrary Shortcode Execution

> Unauthenticated attackers can execute arbitrary shortcodes via crafted testimonials, potentially leading to code execution when administrators preview or publish them.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Nov 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-59gw-wcgq-689r

## What is CVE-2025-11268?

CVE-2025-11268 is a medium-severity cross-site scripting vulnerability in wpchill Strong Testimonials, published on 6 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Strong Testimonials plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 3.2.16. This is due to the software allowing users to submit a testimonial in which a value is not properly validated or sanitized prior to being passed to a do_shortcode call. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes if an administrator previews or publishes a crafted testimonial.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2025-11268 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-11268 is a medium-severity cross-site scripting vulnerability in wpchill Strong Testimonials, published on 6 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-11268 in the wild and no public exploit code.

Affected product: wpchill Strong Testimonials. 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-11268/ (Markdown: https://insights.sbomify.com/CVE-2025-11268/index.md)
```

## Sources

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

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