Security readout for executives and security teams
Plain-English summary
CVE-2022-3708 affects the Web Stories plugin for WordPress through version 1.24.0. An authenticated user could make the website send requests to arbitrary internal or external locations, potentially exposing or changing internal service data reachable from the web server.
Executive priority
Treat as urgent for any WordPress estate using Web Stories. Prioritize external-facing sites and environments with sensitive internal services reachable from the web server.
Technical view
The flaw is server-side request forgery in the Web Stories REST API hotlink proxy endpoint. Insufficient validation of the url parameter allows low-privileged authenticated requests to originate from the WordPress server. The CVSS 3.1 score is 9.6, with high confidentiality and integrity impact.
Likely exposure
Exposure is likely limited to WordPress sites running Web Stories version 1.24.0 or earlier with authenticated users who can reach the affected REST API endpoint.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. The risk is still serious because exploitation requires low privileges and can target services only reachable from the server side.
Researcher notes
The affected component is the /v1/hotlink/proxy REST API endpoint. Sources attribute the issue to insufficient validation of the url parameter. GitHub references compare version 1.24.0 to 1.25.0 and identify a related commit, but exploit-in-the-wild evidence was not provided.
Mitigation direction
- Upgrade Web Stories beyond version 1.24.0 after checking vendor guidance.
- Disable or remove the plugin where immediate upgrade is not possible.
- Review WordPress user accounts and remove unnecessary authenticated access.
- Restrict server egress to internal metadata and administrative services where feasible.
- Monitor WordPress and web server logs for unusual REST proxy activity.
Validation and detection
- Inventory WordPress sites for the Web Stories plugin.
- Confirm no deployed instance runs Web Stories 1.24.0 or earlier.
- Check whether the hotlink proxy REST endpoint is reachable by authenticated users.
- Review logs for unexpected requests involving the proxy endpoint or url parameter.
- Validate the plugin update in staging before production rollout.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2022-3708 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N3.15.8Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.6CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/7817a840-325a-4709-8374-84bb32d98d0e?source=cveCVE reference
- https://wordpress.org/plugins/web-storiesCVE reference
- https://github.com/GoogleForCreators/web-stories-wp/compare/v1.24.0...v1.25.0CVE reference
- https://github.com/GoogleForCreators/web-stories-wp/commit/3ad2099f95155d658624ffac2e34ce0da739e34bCVE reference
- https://www.wordfence.com/vulnerability-advisories-continued/#CVE-2022-3708CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.