LiveActive security incident?Get immediate response
CVE Record

CVE-2023-48317: WordPress Display Custom Post Plugin <= 2.2.1 is vulnerable to Cross Site Scripting (XSS)

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Vikas Vatsa Display Custom Post allows Stored XSS.This issue affects Display Custom Post: from n/a through 2.2.1.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-48317 affects the WordPress Display Custom Post plugin through version 2.2.1. It is a stored cross-site scripting issue, meaning unsafe content could be saved and later shown to another user in a browser. Business impact is moderate: it may support account misuse or content tampering, but requires low privileges and user interaction.

Executive priority

Treat as a normal-priority WordPress plugin remediation item. Prioritize internet-facing sites, sites with many contributors, and administrator-facing workflows where stored XSS could affect privileged users.

Technical view

The CVE records CWE-79 improper neutralization during webpage generation in Vikas Vatsa Display Custom Post. CVSS 3.1 is 6.5: network exploitable, low complexity, low privileges required, user interaction required, changed scope, and low confidentiality, integrity, and availability impact. The source bundle does not identify the vulnerable parameter, route, or fixed version.

Likely exposure

Exposure is likely limited to WordPress sites with the Display Custom Post plugin installed at version 2.2.1 or earlier. Sites without the plugin are not affected by this CVE.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. Exploitation would require an authenticated low-privilege context and a victim viewing affected generated content.

Researcher notes

Evidence is limited to the CVE and Patchstack reference metadata. The bundle supports stored XSS, affected versions through 2.2.1, CWE-79, and CVSS 6.5. It does not provide exploit details, affected input locations, proof of exploitation, or a named patched release.

Mitigation direction

  • Inventory WordPress sites for the Display Custom Post plugin.
  • Confirm whether any installed version is 2.2.1 or earlier.
  • Check vendor or Patchstack guidance for a fixed version or mitigation.
  • Disable or remove the plugin where risk is unacceptable and no fix is available.
  • Restrict plugin-related publishing access to trusted users until resolved.

Validation and detection

  • Review plugin inventories across production and staging WordPress sites.
  • Confirm installed plugin slug packageName is display-custom-post.
  • Record exact plugin versions and flag versions through 2.2.1.
  • Review plugin-rendered content paths for unexpected script markup.
  • Validate any remediation first in staging, then recheck production versions.
Prepared
Confidence
medium
Sources
3

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

CWE-79: 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 lookup
cve · low confidence lookup

CVE-2023-48317 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
6.5 (3.1)
Known Exploited
No
Published

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

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
2Source 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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L2.33.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
Vikas VatsaDisplay Custom Postdisplay-custom-post, n/aunaffected
Weakness

CWE details

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

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.