Analyst readout for executives and security teams
Plain-English summary
This WordPress plugin flaw lets an attacker trick a logged-in site administrator into changing WP Meta SEO settings. It is not a direct unauthenticated takeover, but it can alter plugin options and affect site configuration if an administrator clicks a malicious link or visits a crafted page.
Executive priority
Handle during the next WordPress plugin maintenance window unless the plugin is internet-facing on a high-value site with many administrators. Prioritize confirmation and upgrade, but this is not evidenced as actively exploited in the supplied sources.
Technical view
CVE-2023-1028 is a CSRF issue in WP Meta SEO up to and including 4.5.3. Missing or incorrect nonce validation in setIgnore allows forged requests to update plugin options when an authenticated administrator performs attacker-induced browser actions. CVSS 3.1 is 4.3, with required user interaction and low integrity impact.
Likely exposure
WordPress sites using JoomUnited WP Meta SEO versions 4.5.3 or earlier are the relevant exposure. The risk is highest where administrators browse email or external sites while authenticated to WordPress.
Exploitation context
The supplied sources do not state active exploitation, and KEV status is false. Exploitation requires social engineering a site administrator into performing an action that sends a forged request from their authenticated browser session.
Researcher notes
Primary evidence identifies CWE-352 and missing nonce validation in setIgnore. The source bundle’s affected-product metadata is sparse, so rely on the narrative version range and Wordfence reference. Do not assume confidentiality or availability impact beyond the stated low integrity impact.
Mitigation direction
- Upgrade WP Meta SEO beyond 4.5.3; the cited WordPress change references 4.5.4.
- Check vendor and WordPress plugin guidance for the current fixed release.
- Restrict WordPress administrator access to trusted users and managed devices.
- Remind administrators not to open unsolicited links while logged into WordPress.
Validation and detection
- Inventory WordPress sites for active WP Meta SEO installations.
- Confirm the installed WP Meta SEO version is newer than 4.5.3.
- Review plugin changelog or code for nonce validation around setIgnore.
- Check logs for unexpected WP Meta SEO option changes by administrators.
Public sources used
Based on public source material and reviewed before publication.
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-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-1028 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
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/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:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/6b978749-7ea5-45f4-9f69-66a19c0e39ca?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/2870465/wp-meta-seo/tags/4.5.4/inc/class.metaseo-admin.phpCVE reference
- https://www.wordfence.com/threat-intel/vulnerabilities/id/6b978749-7ea5-45f4-9f69-66a19c0e39caCVE 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.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.