# CVE-2021-24684: PDF Light Viewer < 1.4.12 - Authenticated Command Injection

> Authenticated attackers with Author roles can execute arbitrary OS commands on the server via Ghostscript invocation in the PDF Light Viewer plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 18 Oct 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-25m3-pw7x-34hv

## What is CVE-2021-24684?

CVE-2021-24684 is a high-severity command injection vulnerability in Unknown WordPress PDF Light Viewer Plugin, published on 18 Oct 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WordPress PDF Light Viewer Plugin WordPress plugin before 1.4.12 allows users with Author roles to execute arbitrary OS command on the server via OS Command Injection when invoking Ghostscript.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2021-24684?

It affects 1 product.


Products: Teamlead Pdf-Light-Viewer.

## How do I fix CVE-2021-24684?

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

## Is CVE-2021-24684 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-24684 and fix it if it is affected.

What it is: CVE-2021-24684 is a high-severity command injection vulnerability in Unknown WordPress PDF Light Viewer Plugin, published on 18 Oct 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-24684 in the wild and no public exploit code.

Affected product: Unknown WordPress PDF Light Viewer Plugin. 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-2021-24684/ (Markdown: https://insights.sbomify.com/CVE-2021-24684/index.md)
```

## Sources

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

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