Security readout for executives and security teams
Plain-English summary
A flaw in Yoast SEO Premium for WordPress allowed unauthenticated users to reset the plugin’s Zapier API key. The documented impact is limited to availability: disrupted automation or integration behavior, not data theft or content changes. Sites using Yoast SEO Premium 20.4 or earlier should be checked against vendor guidance.
Executive priority
Handle in normal vulnerability management cadence, with higher priority for business-critical WordPress sites dependent on Zapier automations.
Technical view
CVE-2023-28775 is a missing authorization issue (CWE-862) in Yoast SEO Premium through version 20.4. The CVSS 3.1 score is 5.3, network exploitable, low complexity, no privileges, no user interaction, with availability impact only.
Likely exposure
Exposure is likely limited to WordPress sites running Yoast SEO Premium version 20.4 or earlier, especially where Zapier integration is configured or operationally important.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Treat this as remotely reachable but moderate-impact until vendor or monitoring evidence indicates otherwise.
Researcher notes
Evidence supports missing authorization and availability impact only. The public bundle does not provide exploit details, confirmed exploitation, or a named fixed version; validation should stay version- and configuration-focused.
Mitigation direction
- Inventory WordPress sites running Yoast SEO Premium.
- Check plugin versions and flag 20.4 or earlier.
- Review Yoast and Patchstack guidance for the fixed version.
- Upgrade beyond 20.4 if vendor guidance confirms remediation.
- Review Zapier integrations for unexpected key resets or failures.
Validation and detection
- Confirm installed Yoast SEO Premium versions across WordPress environments.
- Verify whether affected sites use the Zapier integration.
- Review web and application logs for unusual unauthenticated plugin activity.
- Check Zapier automation health after any suspected reset.
- Document remediation status per site and plugin version.
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-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookupCVE-2023-28775 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
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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:N/UI:N/S:U/C:N/I:N/A:L3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Source materials
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.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.