Easy Video PlayerWordPress extension · Noorsplugin
CVE-2023-51689
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in naa986 Easy Video Player allows Stored XSS.This issue affects Easy Video Player: from n/a through 1.2.2.10.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA stored cross-site scripting (XSS) vulnerability exists in the naa986 Easy Video Player plugin (versions through 1.2.2.10) where user-supplied input is not properly sanitized before being rendered in web pages, allowing malicious JavaScript to be persisted and executed in the context of other users' browsers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Easy Video PlayerWordPress extension
<= 1.2.2.10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Easy Video Player is installedAccess WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'Easy Video Player' by naa986 or Noorsplugin in the listAffected if The plugin appears in the installed plugins list
-
Identify the installed versionIn the Plugins list, find Easy Video Player and note the version number displayed beneath the plugin nameAffected if Version is 1.2.2.10 or lower (any version through 1.2.2.10)
-
Locate video content created with the pluginCheck pages and posts for embedded videos using the Easy Video Player shortcode (typically [evp_embed_video] or similar), or review any custom video post type if the plugin creates oneAffected if Any video content exists on the site
-
Inspect stored video parameters for unsanitized inputEdit each video entry and examine fields such as video URL, title, description, or custom player settings for any input containing HTML, JavaScript, or script-related characters (<, >, script, javascript:, onerror, etc.)Affected if Any video entry contains raw HTML/script tags or suspicious characters in user-editable fields that could execute as JavaScript in a visitor's browser
You are affected if Easy Video Player version 1.2.2.10 or lower is installed AND any video entries contain unsanitized user-supplied input that could execute as JavaScript when viewed by other users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper input validation and output encoding/escaping on all user-supplied data before storage and display. Update to the latest version of Easy Video Player when a patched release becomes available.
Fix this in Easy Video Player
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-51689 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-51689 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data