# CVE-2022-0661: Ad Injection <= 1.2.0.19 - Admin+ Stored Cross-Site Scripting & RCE

> Admins can inject PHP code for remote code execution and HTML/JS for stored XSS in the Ad Injection WordPress plugin.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Apr 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-g5jf-j433-qxmq

## What is CVE-2022-0661?

CVE-2022-0661 is a high-severity code injection vulnerability in Unknown Ad Injection, published on 18 Apr 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Ad Injection WordPress plugin through 1.2.0.19 does not properly sanitize the body of the adverts injected into the pages, allowing a high privileged user (Admin+) to inject arbitrary HTML or javascript even with unfiltered_html disallowed, leading to a stored cross-site scripting (XSS) vulnerability. Further it is also possible to inject PHP code, leading to a Remote Code execution (RCE) vulnerability, even if the DISALLOW_FILE_EDIT and DISALLOW_FILE_MOD constants are both set.

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

## Which versions are affected by CVE-2022-0661?

It affects 1 product.


Products: Ad Injection Project Ad Injection.

## How do I fix CVE-2022-0661?

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

## Is CVE-2022-0661 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0661 and fix it if it is affected.

What it is: CVE-2022-0661 is a high-severity code injection vulnerability in Unknown Ad Injection, published on 18 Apr 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-0661 in the wild and no public exploit code.

Affected product: Unknown Ad Injection. 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-2022-0661/ (Markdown: https://insights.sbomify.com/CVE-2022-0661/index.md)
```

## Sources

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

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