LiveActive security incident?Get immediate response
CVE Record

CVE-2023-6983: Display custom fields in the frontend – Post and User Profile Fields <= 1.2.1 - Insecure Direct Object Reference to Authenticated (Contributor+) Post Meta Disclosure

The Display custom fields in the frontend – Post and User Profile Fields plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.2.1 via the vg_display_data shortcode due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with contributor-level access and above, to retrieve potentially sensitive post meta.

MediumCVSS 4.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A WordPress plugin can let logged-in users with contributor-level access or higher read post metadata they should not see. The business risk is data exposure, not site takeover, based on the provided CVSS and description.

Executive priority

Prioritize remediation on sites with external contributors, customer data, private content workflows, or sensitive metadata. Lower urgency for sites without the plugin or without contributor-plus untrusted users.

Technical view

CVE-2023-6983 is an IDOR/CWE-639 in the Display custom fields in the frontend plugin through version 1.2.1. The vg_display_data shortcode lacks validation on a user-controlled key, allowing authenticated contributor-plus users to retrieve potentially sensitive post meta.

Likely exposure

Exposure is limited to WordPress sites using this plugin at version 1.2.1 or earlier, especially where untrusted or numerous contributor-level accounts exist.

Exploitation context

The bundle does not state active exploitation, and KEV is false. Exploitation requires authenticated contributor-level or higher access and targets confidentiality of post metadata.

Researcher notes

The description and title identify versions through 1.2.1 as vulnerable. The structured affected block is sparse and should be reconciled against vendor or WordPress.org plugin metadata before broad asset conclusions.

Mitigation direction

  • Inventory WordPress sites for this plugin and version.
  • Update to a vendor-provided fixed release if available.
  • Disable or remove the plugin if no fixed release is available.
  • Restrict contributor-level access to trusted users only.
  • Avoid storing secrets or sensitive records in post meta.

Validation and detection

  • Confirm whether the plugin is installed and version is <= 1.2.1.
  • Review contributor, author, editor, and administrator account assignments.
  • Identify pages or posts using the vg_display_data shortcode.
  • Check whether sensitive information exists in post meta.
  • Review authenticated access logs for unusual metadata access patterns.
Prepared
Confidence
high
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookup
cve · low confidence lookup

CVE-2023-6983 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2023-6983Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
josevegaDisplay custom fields in the frontend – Post and User Profile Fields0unaffected
Weakness

CWE details

CWE-639

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs