LiveActive security incident?Get immediate response
CVE Record

CVE-2023-48320: WordPress Video Player Plugin <= 1.5.22 is vulnerable to Cross Site Scripting (XSS)

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WebDorado SpiderVPlayer allows Stored XSS.This issue affects SpiderVPlayer: from n/a through 1.5.22.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE affects WordPress sites using WebDorado SpiderVPlayer through version 1.5.22. A highly privileged user could store malicious script content that runs when another user views the affected page. The CVSS score is medium, but impact depends on who can manage plugin content and who later views it.

Executive priority

Treat as a moderate-priority WordPress plugin exposure. It is not currently supported by cited active-exploitation evidence, but stored XSS can affect user trust and admin sessions. Prioritize sites where many users view video pages or where plugin editors are not tightly controlled.

Technical view

CVE-2023-48320 is a stored XSS issue in WebDorado SpiderVPlayer caused by improper output neutralization during web page generation. The CVSS 3.1 vector is AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L, indicating network reachability, high privileges, user interaction, changed scope, and low confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress deployments with WebDorado SpiderVPlayer, also referenced as package player, through version 1.5.22. Sites without this plugin are not indicated as affected by the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. The CVSS vector indicates exploitation requires high privileges and a user to view affected generated content. Public details in the bundle do not identify the exact field, page, or payload behavior.

Researcher notes

Evidence is incomplete for vulnerable parameters, fixed version, and exploit availability. Use the CVSS vector and CWE-79 classification to guide triage. Avoid assuming unauthenticated exploitability; the provided score explicitly requires high privileges and user interaction.

Mitigation direction

  • Inventory WordPress sites for SpiderVPlayer/player versions through 1.5.22.
  • Check WebDorado and Patchstack guidance for a patched version or removal recommendation.
  • Restrict plugin administration to trusted accounts pending vendor guidance.
  • Disable or remove the plugin where it is not business-critical.

Validation and detection

  • Confirm whether SpiderVPlayer/player is installed on each WordPress site.
  • Record installed plugin versions and flag versions through 1.5.22.
  • Review who has privileges to manage plugin content.
  • Check vendor and Patchstack advisories for current remediation details.
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-48320 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
5.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/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
5.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L1.73.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:H/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
WebDoradoSpiderVPlayerplayer, 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.