# CVE-2022-1695: WP Simple Adsense Insertion < 2.1 - Inject ads and javascript via CSRF

> Attackers can trick logged-in users into injecting arbitrary JavaScript and modifying ads via CSRF in the WP Simple Adsense Insertion plugin.

- **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 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-r95m-cpg7-2vpv

## What is CVE-2022-1695?

CVE-2022-1695 is a medium-severity vulnerability in Unknown WP Simple Adsense Insertion, published on 6 Jun 2022. 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 WP Simple Adsense Insertion WordPress plugin before 2.1 does not perform CSRF checks on updates to its admin page, allowing an attacker to trick a logged in user to manipulate ads and inject arbitrary javascript via submitting a form.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Tipsandtricks-Hq Wp Simple Adsense Insertion.

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

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

## Is CVE-2022-1695 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1695 is a medium-severity vulnerability in Unknown WP Simple Adsense Insertion, published on 6 Jun 2022. 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-2022-1695 in the wild and no public exploit code.

Affected product: Unknown WP Simple Adsense Insertion. 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-1695/ (Markdown: https://insights.sbomify.com/CVE-2022-1695/index.md)
```

## Sources

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

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