Security readout for executives and security teams
Plain-English summary
A low-privileged WordPress user could change WP Meta SEO sitemap settings on sites running vulnerable versions. The issue does not require admin rights and could affect search visibility or sitemap behavior, but the provided sources do not show data theft, full site takeover, or active exploitation.
Executive priority
Treat as a moderate-priority plugin governance issue. Prioritize faster where public registration, customer accounts, or SEO visibility are business-critical.
Technical view
WP Meta SEO through 4.5.3 lacks a capability check in saveSitemapSettings. The plugin relied on nonce checks for access control, and the nonce was available to authenticated users regardless of role. This is CWE-862 with CVSS 3.1 score 5.4.
Likely exposure
Exposure is limited to WordPress sites using WP Meta SEO versions up to and including 4.5.3 where an attacker has any authenticated account, including subscriber-level access.
Exploitation context
The provided sources support authenticated low-privilege misuse of sitemap settings. CISA KEV is false, and no supplied source states active exploitation in the wild.
Researcher notes
The source bundle identifies missing authorization, not nonce bypass. Validate role-based access control around saveSitemapSettings and compare against the referenced WordPress plugin changeset for the corrected authorization pattern.
Mitigation direction
- Upgrade WP Meta SEO beyond affected versions using vendor guidance.
- If updating is not immediately possible, disable the plugin temporarily.
- Limit unnecessary subscriber accounts and public registration.
- Review sitemap settings after remediation for unexpected changes.
Validation and detection
- Inventory WordPress sites for WP Meta SEO installations.
- Confirm whether installed versions are 4.5.3 or earlier.
- Check whether public registration or subscriber accounts are enabled.
- Review sitemap settings and recent plugin configuration changes.
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-1023 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.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:L/UI:N/S:U/C:N/I:L/A:L2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/9d1e498a-ddcb-4c67-bf0d-bb45b6fe0e9d?source=cveCVE reference
- https://plugins.trac.wordpress.org/changeset/2870465/wp-meta-seo/trunk?contextall=1&old=2869205&old_path=%2Fwp-meta-seo%2Ftrunk#file2CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=2870465%40wp-meta-seo&new=2870465%40wp-meta-seo&sfp_email=&sfph_mail=CVE reference
- https://www.wordfence.com/threat-intel/vulnerabilities/id/9d1e498a-ddcb-4c67-bf0d-bb45b6fe0e9dCVE reference · x_transferred
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.