# CVE-2025-48119: WordPress RS WP Book Showcase plugin <= 6.7.59 - Content Injection vulnerability

> Attackers can inject malicious code into the RS WP Book Showcase plugin, potentially leading to remote code execution on the WordPress site.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 16 May 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-xhqg-qw3g-gfc2

## What is CVE-2025-48119?

CVE-2025-48119 is a medium-severity code injection vulnerability in RS WP Book Showcase, published on 16 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Control of Generation of Code ('Code Injection') vulnerability in RS WP THEMES RS WP Book Showcase rs-wp-books-showcase allows Code Injection.This issue affects RS WP Book Showcase: from n/a through <= 6.7.59.

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

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


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

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

## Is CVE-2025-48119 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-48119 is a medium-severity code injection vulnerability in RS WP Book Showcase, published on 16 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-48119 in the wild and no public exploit code.

Affected product: RS WP Book Showcase. 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-48119/ (Markdown: https://insights.sbomify.com/CVE-2025-48119/index.md)
```

## Sources

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

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