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-2410: CWE-352 Cross-Site Request Forgery (CSRF) in themeisle Disable Admin Notices – Hide Dashboard Notifications

0
Medium
VulnerabilityCVE-2026-2410cvecve-2026-2410cwe-352
Published: Wed Feb 25 2026 (02/25/2026, 09:26:50 UTC)
Source: CVE Database V5
Vendor/Project: themeisle
Product: Disable Admin Notices – Hide Dashboard Notifications

Description

CVE-2026-2410 is a Cross-Site Request Forgery (CSRF) vulnerability affecting the WordPress plugin 'Disable Admin Notices – Hide Dashboard Notifications' up to version 1. 4. 2. The flaw arises from missing nonce validation in the showPageContent() function, allowing unauthenticated attackers to craft malicious requests that can add arbitrary URLs to the blocked redirects list. Exploitation requires tricking an authenticated site administrator into clicking a specially crafted link, enabling the attacker to manipulate plugin settings without direct authentication. The vulnerability impacts the integrity of the plugin’s configuration but does not affect confidentiality or availability. The CVSS 3. 1 base score is 4. 3 (medium severity), reflecting the need for user interaction and limited impact scope. No known exploits are currently reported in the wild.

AI-Powered Analysis

AILast updated: 02/25/2026, 09:55:49 UTC

Technical Analysis

CVE-2026-2410 is a medium-severity CSRF vulnerability identified in the WordPress plugin 'Disable Admin Notices – Hide Dashboard Notifications' developed by themeisle. The vulnerability exists in all versions up to and including 1.4.2 due to the absence of nonce validation in the showPageContent() function, which is responsible for rendering plugin settings pages. Nonce tokens are security mechanisms used in WordPress to verify that requests originate from legitimate users and not from forged sources. Without nonce validation, attackers can craft malicious URLs or forms that, when visited or submitted by an authenticated administrator, cause unintended changes to the plugin’s configuration. Specifically, attackers can add arbitrary URLs to the blocked redirects list, potentially interfering with site navigation or administrative notice management. Exploitation requires social engineering to convince an administrator to click a malicious link or visit a crafted page, as no authentication is required for the attacker but user interaction is mandatory. The vulnerability impacts the integrity of plugin settings but does not expose sensitive data or cause denial of service. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N) indicates network attack vector, low attack complexity, no privileges required, user interaction required, unchanged scope, no confidentiality or availability impact, and limited integrity impact. No public exploits or active exploitation have been reported to date. The vulnerability was published on February 25, 2026, and remains unpatched as no patch links are provided. This issue highlights the importance of implementing nonce validation in WordPress plugins to prevent CSRF attacks.

Potential Impact

The primary impact of CVE-2026-2410 is the unauthorized modification of plugin settings by an attacker through CSRF, which compromises the integrity of the affected WordPress site’s administrative configuration. By adding arbitrary URLs to the blocked redirects list, attackers can disrupt normal administrative workflows, potentially causing confusion or hindering legitimate administrative notices. Although this does not directly expose sensitive data or cause service outages, it may facilitate further social engineering or administrative errors. For organizations relying on this plugin, especially those with multiple administrators or complex workflows, this vulnerability could lead to misconfigurations that degrade user experience or complicate site management. Since exploitation requires an administrator to interact with a malicious link, the risk is somewhat mitigated by user awareness but remains significant in environments with less vigilant users. The absence of known exploits reduces immediate risk but does not eliminate the potential for future attacks. Overall, the impact is medium severity, affecting integrity without compromising confidentiality or availability.

Mitigation Recommendations

To mitigate CVE-2026-2410, organizations should immediately update the 'Disable Admin Notices – Hide Dashboard Notifications' plugin to a version that includes nonce validation once available. Until a patch is released, administrators should avoid clicking on suspicious links and be cautious when browsing untrusted websites. Implementing web application firewalls (WAFs) with rules to detect and block CSRF attempts targeting the plugin’s endpoints can provide additional protection. Site administrators should enforce the principle of least privilege by limiting administrative access to trusted personnel only. Enabling multi-factor authentication (MFA) for WordPress admin accounts can reduce the risk of account compromise that could facilitate exploitation. Regularly auditing plugin configurations and monitoring for unexpected changes to the blocked redirects list can help detect exploitation attempts early. Developers maintaining WordPress plugins should ensure nonce validation is implemented for all state-changing requests to prevent similar CSRF vulnerabilities. Finally, educating administrators about the risks of CSRF and safe browsing practices is essential to reduce the likelihood of successful social engineering attacks.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2026-02-12T15:19:11.579Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699ec3cbb7ef31ef0bf52b19

Added to database: 2/25/2026, 9:41:31 AM

Last enriched: 2/25/2026, 9:55:49 AM

Last updated: 2/25/2026, 11:59:57 AM

Views: 8

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