Security readout for executives and security teams
Plain-English summary
A WordPress plugin can let a logged-in user with Contributor-level access or higher trigger code execution through a shortcode. If the plugin is installed on a site with untrusted or compromised contributor accounts, the impact can include full site compromise.
Executive priority
Treat this as urgent for public WordPress sites using the plugin with multiple content users. Prioritize inventory and containment because the reported impact is code execution, not just data exposure.
Technical view
CVE-2023-6996 is CWE-94 code injection in the Display custom fields in the frontend plugin through the vg_display_data shortcode. Versions up to and including 1.2.1 lack sufficient input validation and shortcode access restriction, allowing authenticated Contributor+ users to call arbitrary functions and execute code.
Likely exposure
Exposure is most likely on WordPress sites running this plugin at version 1.2.1 or older, especially where Contributor, Author, Editor, or Administrator accounts are externally managed, numerous, dormant, or weakly protected.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The attacker needs authenticated Contributor-level or higher access, but successful exploitation could affect confidentiality, integrity, and availability.
Researcher notes
The strongest evidence is the CVE description and Wordfence reference. Patch details are not fully described in the supplied bundle beyond a WordPress Trac changeset, so avoid assuming a specific fixed version unless confirmed from vendor sources.
Mitigation direction
- Inventory WordPress sites for this plugin and version 1.2.1 or older.
- Check vendor and WordPress plugin guidance for the fixed release before upgrading.
- Disable or remove the plugin if no verified fixed version is available.
- Restrict Contributor-level access to trusted users only.
- Review and harden account security for all WordPress users with content privileges.
Validation and detection
- Confirm whether the plugin is installed and record its exact version.
- Review user roles for Contributor-level or higher accounts that are unnecessary or stale.
- Inspect content for unexpected use of the vg_display_data shortcode.
- Review application logs for suspicious activity by authenticated content users.
- Verify remediation against vendor guidance after upgrade, removal, or disablement.
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-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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-6996 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
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/e0662c3a-5b82-4b9a-aa69-147094930d1f?source=cveCVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3021133%40shortcode-to-display-post-and-user-data&new=3021133%40shortcode-to-display-post-and-user-data&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.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.