# CVE-2022-1672: Insights from Google PageSpeed < 4.0.7 - Multiple CSRF

> Attackers can trick logged-in admins into deleting custom URLs via CSRF, requiring an upgrade to the Insights from Google PageSpeed plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 17 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-28mj-h58q-vmmm

## What is CVE-2022-1672?

CVE-2022-1672 is a high-severity vulnerability in Unknown Insights from Google PageSpeed, published on 17 Jul 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 Insights from Google PageSpeed WordPress plugin before 4.0.7 does not verify for CSRF before doing various actions such as deleting Custom URLs, which could allow attackers to make a logged in admin perform such actions via CSRF attacks

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

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

It affects 1 product.


Products: Insights From Google Pagespeed Project Insights From Google Pagespeed.

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

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

## Is CVE-2022-1672 being exploited?

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

## Other vulnerabilities in Unknown Insights from Google PageSpeed

- [CVE-2022-0431](https://insights.sbomify.com/CVE-2022-0431/): Google Pagespeed Insights < 4.0.4 - Reflected Cross-Site Scripting (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1672 is a high-severity vulnerability in Unknown Insights from Google PageSpeed, published on 17 Jul 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-1672 in the wild and no public exploit code.

Affected product: Unknown Insights from Google PageSpeed. 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-1672/ (Markdown: https://insights.sbomify.com/CVE-2022-1672/index.md)
```

## Sources

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

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