Security readout for executives and security teams
Plain-English summary
CVE-2026-2023 affects the WP Plugin Info Card WordPress plugin through version 6.2.0. A malicious site or link could cause a logged-in administrator’s browser to create or modify custom plugin entries without proper request verification. Business impact appears limited to unauthorized content or configuration changes, but affected public WordPress sites should be reviewed.
Executive priority
Treat as a timely WordPress hygiene issue, not an emergency based on current sources. Prioritize internet-facing or high-value sites where administrators may be targeted by phishing, and remediate during the next security maintenance window unless signs of abuse appear.
Technical view
The issue is a CSRF flaw in ajax_save_custom_plugin() caused by missing nonce validation; the check is reportedly disabled with a false && condition. Sources describe unauthenticated attackers inducing an administrator action to create or modify custom plugin entries. CVSS 3.1 is 4.3, with low integrity impact and required user interaction.
Likely exposure
WordPress sites using WP Plugin Info Card versions up to and including 6.2.0 are the stated exposure. The administrator must be authenticated and tricked into an action for abuse to occur.
Exploitation context
The source bundle does not indicate CISA KEV listing or confirmed active exploitation. Exploitation depends on social engineering of a site administrator and results in unauthorized custom plugin entry creation or modification, not direct server compromise in the cited description.
Researcher notes
Evidence points to CWE-352 CSRF in the admin AJAX save path with nonce validation intentionally bypassed in code. The CVE description names affected versions through 6.2.0, but the provided sources do not clearly state a fixed version. Avoid assuming exploit activity without additional evidence.
Mitigation direction
- Identify all WordPress sites running WP Plugin Info Card.
- Check whether installed versions are 6.2.0 or older.
- Review vendor, WordPress.org, and Wordfence guidance for fixed release information.
- Update the plugin if a vendor-supported fixed version is available.
- If no fix is available, consider disabling the plugin until vendor guidance is clear.
Validation and detection
- Inventory WordPress plugins across production, staging, and managed hosting accounts.
- Confirm WP Plugin Info Card version from WordPress admin or asset inventory.
- Review custom plugin entries for unexpected additions or changes.
- Check application logs for suspicious administrator-session changes to plugin entries.
- Track the referenced Wordfence and WordPress.org plugin pages for remediation updates.
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-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-2026-2023 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/1213a21f-a9c1-4da3-99b5-4a5a0673073f?source=cveCVE reference
- https://github.com/DLXPlugins/wp-plugin-info-card/blob/0fe50d3ccb3d61d5d176fab9e9f280ac8bfd8614/php/Admin/Init.php#L390CVE reference
- https://plugins.trac.wordpress.org/browser/wp-plugin-info-card/tags/6.2.0/php/Admin/Init.php#L390CVE reference
- https://plugins.trac.wordpress.org/browser/wp-plugin-info-card/trunk/php/Admin/Init.php#L390CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3454992%40wp-plugin-info-card&new=3454992%40wp-plugin-info-card&sfp_email=&sfph_mail=CVE 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.
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.