# CVE-2022-3708: Web Stories <= 1.24.0 - Server Side Request Forgery

> Authenticated users can exploit SSRF in the Web Stories plugin to query and modify internal services via the hotlink proxy endpoint.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N`)
- **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:** 28 Oct 2022
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-ph82-g2mr-p678

## What is CVE-2022-3708?

CVE-2022-3708 is a critical server-side request forgery vulnerability in google Web Stories, published on 28 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Web Stories plugin for WordPress is vulnerable to Server-Side Request Forgery in versions up to, and including 1.24.0 due to insufficient validation of URLs supplied via the 'url' parameter found via the /v1/hotlink/proxy REST API Endpoint. This makes it possible for authenticated users to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Google Web Stories.

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

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

## Is CVE-2022-3708 being exploited?

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

## Other vulnerabilities in google Web Stories

- [CVE-2023-1979](https://insights.sbomify.com/CVE-2023-1979/): Auth bypass in Web Stories for WordPress plugin (medium 4.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3708 is a critical server-side request forgery vulnerability in google Web Stories, published on 28 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-3708 in the wild and no public exploit code.

Affected product: google Web Stories. 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-3708/ (Markdown: https://insights.sbomify.com/CVE-2022-3708/index.md)
```

## Sources

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

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