# CVE-2025-13418: Responsive Pricing Table <= 5.1.12 - Authenticated (Author+) Stored Cross-Site Scripting

> Authenticated attackers with Author access can inject arbitrary scripts via the plan_icons parameter, leading to stored XSS execution for other users.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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:** 7 Jan 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-6qvx-xqgf-3cvh

## What is CVE-2025-13418?

CVE-2025-13418 is a medium-severity cross-site scripting vulnerability in spwebguy Responsive Pricing Table, published on 7 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Responsive Pricing Table plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'plan_icons' parameter in all versions up to, and including, 5.1.12 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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

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


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

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

## Is CVE-2025-13418 being exploited?

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

Public exploit code:

- Responsive Pricing Table <= 5.1.12 - Cross-Site Scripting (nuclei): http/cves/2025/CVE-2025-13418.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13418 is a medium-severity cross-site scripting vulnerability in spwebguy Responsive Pricing Table, published on 7 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-13418 exists.

Affected product: spwebguy Responsive Pricing Table. 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-13418/ (Markdown: https://insights.sbomify.com/CVE-2025-13418/index.md)
```

## Sources

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

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