Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-0724: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in wecodify WPlyr Media Block

0
Medium
VulnerabilityCVE-2026-0724cvecve-2026-0724cwe-79
Published: Wed Feb 11 2026 (02/11/2026, 08:26:26 UTC)
Source: CVE Database V5
Vendor/Project: wecodify
Product: WPlyr Media Block

Description

The WPlyr Media Block plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the '_wplyr_accent_color' parameter in all versions up to, and including, 1.3.0 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with Administrator-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/26/2026, 18:38:08 UTC

Technical Analysis

CVE-2026-0724 is a stored Cross-Site Scripting (XSS) vulnerability classified under CWE-79 affecting the WPlyr Media Block plugin for WordPress, versions up to and including 1.3.0. The vulnerability stems from insufficient input sanitization and output escaping of the '_wplyr_accent_color' parameter, which is user-supplied. Authenticated attackers with Administrator-level access or higher can exploit this flaw by injecting arbitrary JavaScript code into pages generated by the plugin. Because the malicious script is stored persistently, it executes whenever any user views the infected page, potentially compromising user sessions, stealing cookies, or performing actions on behalf of users. The attack vector is network-based, requiring high privileges (administrator) but no user interaction. The CVSS v3.1 base score is 4.4, reflecting a medium severity due to limited impact on confidentiality and integrity and no impact on availability. The vulnerability affects all versions of the plugin up to 1.3.0, with no patches currently available. No known exploits have been observed in the wild, but the risk remains significant for sites with multiple administrators or high-value content. The vulnerability highlights the importance of proper input validation and output encoding in web applications to prevent XSS attacks.

Potential Impact

The primary impact of CVE-2026-0724 is the potential for attackers with administrator privileges to inject persistent malicious scripts into WordPress pages, which execute in the browsers of any users who visit those pages. This can lead to session hijacking, theft of authentication tokens, unauthorized actions performed on behalf of users, and potential privilege escalation if combined with other vulnerabilities. Although exploitation requires administrator access, which limits the attack surface, compromised administrator accounts or insider threats could leverage this vulnerability to escalate damage. The vulnerability does not affect availability directly but can undermine the integrity and confidentiality of user data and site content. For organizations relying on WordPress with the WPlyr Media Block plugin, this could result in reputational damage, data breaches, and loss of user trust. The absence of known exploits reduces immediate risk, but the medium CVSS score and stored nature of the XSS make it a persistent threat if left unmitigated.

Mitigation Recommendations

To mitigate CVE-2026-0724, organizations should first verify if they use the WPlyr Media Block plugin and identify the version in use. Since no official patch is currently available, immediate steps include restricting administrator access to trusted personnel only and auditing existing content for injected scripts. Implementing a Web Application Firewall (WAF) with rules to detect and block malicious script injection attempts targeting the '_wplyr_accent_color' parameter can reduce risk. Additionally, applying strict Content Security Policy (CSP) headers can limit the execution of unauthorized scripts. Site administrators should monitor logs for suspicious activity and consider temporarily disabling or removing the plugin until a patch is released. Developers and site owners should also ensure that input validation and output encoding best practices are followed in custom code. Regular backups and incident response plans should be in place to recover from potential compromises.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2026-01-08T13:42:18.405Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 698c3e544b57a58fa1832d13

Added to database: 2/11/2026, 8:31:16 AM

Last enriched: 2/26/2026, 6:38:08 PM

Last updated: 4/6/2026, 4:12:15 PM

Views: 34

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses