LiveActive security incident?Get immediate response
CVE Record

CVE-2023-4962: Video PopUp <= 1.1.3 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode

The Video PopUp plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'video_popup' shortcode in versions up to, and including, 1.1.3 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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

Security readout for executives and security teams

Plain-English summary

A user with contributor-level WordPress access could place malicious script into the Video PopUp shortcode on vulnerable sites. That script would run for visitors who view the affected page. This is not listed as known exploited in KEV, but it can still matter on sites with many authors or weak account controls.

Executive priority

Treat this as a targeted content-integrity and visitor-trust risk, not an internet-wide emergency. Patch or remove affected plugin versions promptly, with higher urgency for public sites that allow multiple content contributors.

Technical view

CVE-2023-4962 is stored cross-site scripting in the WordPress Video PopUp plugin through the video_popup shortcode. Sources attribute it to insufficient sanitization and output escaping of user-supplied shortcode attributes in versions up to and including 1.1.3. CVSS is 6.4, network-reachable, low complexity, low privileges required, and scope changed.

Likely exposure

Exposure is most likely on WordPress sites running Video PopUp versions up to and including 1.1.3, especially where contributor, author, editor, or administrator accounts are shared, numerous, or weakly protected.

Exploitation context

The provided sources do not show active exploitation, and KEV is false. Exploitation requires an authenticated account with contributor-level or higher permissions, then depends on someone viewing the page containing the injected shortcode.

Researcher notes

The record names stored XSS via shortcode attributes and cites WordPress Trac code and a changeset. The source bundle does not include exploit details, proof of active exploitation, or a clearly named fixed version, so remediation should be tied to vendor guidance.

Mitigation direction

  • Inventory WordPress sites for the Video PopUp plugin and version.
  • Prioritize any installation at version 1.1.3 or earlier.
  • Check vendor or WordPress plugin guidance for the fixed release.
  • Update, disable, or remove the plugin where a fix is unavailable.
  • Restrict contributor-level publishing access to trusted accounts only.
  • Review pages and posts using the video_popup shortcode.

Validation and detection

  • Confirm the installed Video PopUp version in each WordPress environment.
  • Search content for video_popup shortcode usage.
  • Review recent contributor-or-higher account activity on affected sites.
  • Verify updates include the referenced shortcode sanitization and escaping changes.
  • Check that untrusted users cannot add unsafe shortcode attributes.
Prepared
Confidence
high
Sources
5

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 · 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-4962 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.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/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
4Source 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.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N3.12.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/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
alobaidiVideo PopUp0unaffected
Weakness

CWE details

CWE-79

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