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-0681: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in rtddev Extended Random Number Generator

0
Medium
VulnerabilityCVE-2026-0681cvecve-2026-0681cwe-79
Published: Wed Feb 04 2026 (02/04/2026, 08:25:29 UTC)
Source: CVE Database V5
Vendor/Project: rtddev
Product: Extended Random Number Generator

Description

The Extended Random Number Generator plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin settings in all versions up to, and including, 1.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level access, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.

AI-Powered Analysis

AILast updated: 02/04/2026, 09:00:52 UTC

Technical Analysis

CVE-2026-0681 identifies a stored Cross-Site Scripting (XSS) vulnerability in the Extended Random Number Generator plugin for WordPress, affecting all versions up to and including 1.1. The flaw arises from improper neutralization of input during web page generation (CWE-79), specifically due to insufficient input sanitization and output escaping in the plugin's settings interface. This vulnerability is exploitable only in multi-site WordPress installations where the unfiltered_html capability is disabled, and requires an attacker to have authenticated administrator-level privileges. An attacker with such access can inject arbitrary JavaScript code into plugin settings, which is then stored and executed whenever any user visits the affected pages. This can lead to session hijacking, theft of sensitive information, or further privilege escalation within the WordPress environment. The vulnerability has a CVSS 3.1 base score of 4.4 (medium severity), reflecting that exploitation requires high privileges (PR:H), no user interaction (UI:N), network attack vector (AV:N), and impacts confidentiality and integrity with limited scope. No known public exploits or patches are currently available, increasing the importance of proactive mitigation. The vulnerability specifically targets the Extended Random Number Generator plugin, which is a niche plugin but may be used in specialized WordPress multi-site deployments.

Potential Impact

For European organizations, this vulnerability poses a moderate risk primarily to multi-site WordPress deployments using the Extended Random Number Generator plugin. The requirement for administrator-level access limits the attack surface to insiders or compromised admin accounts, but successful exploitation can lead to unauthorized disclosure of sensitive data and potential further compromise of the WordPress environment. Confidentiality and integrity of user sessions and data can be impacted, potentially exposing personal data protected under GDPR. Although availability is not affected, the reputational damage and compliance risks from data leakage could be significant. Organizations running multi-site WordPress installations with this plugin, especially those hosting multiple client sites or internal portals, are at higher risk. The lack of patches means that mitigation must rely on access control and monitoring until a fix is released.

Mitigation Recommendations

1. Restrict administrator access strictly to trusted personnel and enforce strong authentication mechanisms such as MFA to reduce the risk of credential compromise. 2. Audit all multi-site WordPress installations to identify usage of the Extended Random Number Generator plugin and assess whether unfiltered_html is disabled. 3. Temporarily disable or remove the plugin in multi-site environments if feasible until a patch is available. 4. Implement manual input validation and output escaping for plugin settings if plugin code can be safely modified by qualified developers. 5. Monitor WordPress logs and plugin settings for suspicious changes or injected scripts. 6. Educate administrators about the risks of injecting arbitrary content and the importance of secure plugin management. 7. Keep WordPress core and all plugins updated and subscribe to vendor advisories for timely patch releases. 8. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block suspicious script injections targeting plugin settings pages.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2026-01-07T17:59:41.218Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6983072af9fa50a62f79eb8d

Added to database: 2/4/2026, 8:45:30 AM

Last enriched: 2/4/2026, 9:00:52 AM

Last updated: 2/6/2026, 11:48:14 PM

Views: 24

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 in Console -> Billing for AI refresh and higher limits.

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

Latest Threats