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-2025-5928: CWE-352 Cross-Site Request Forgery (CSRF) in fay-1 WP Sliding Login/Dashboard Panel

0
Medium
VulnerabilityCVE-2025-5928cvecve-2025-5928cwe-352
Published: Fri Jun 13 2025 (06/13/2025, 01:47:51 UTC)
Source: CVE Database V5
Vendor/Project: fay-1
Product: WP Sliding Login/Dashboard Panel

Description

The WP Sliding Login/Dashboard Panel plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.1.1. This is due to missing or incorrect nonce validation on the wp_sliding_panel_user_options() function. This makes it possible for unauthenticated attackers to update plugin settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 15:40:58 UTC

Technical Analysis

CVE-2025-5928 identifies a Cross-Site Request Forgery vulnerability in the WP Sliding Login/Dashboard Panel plugin for WordPress, affecting all versions up to and including 2.1.1. The vulnerability stems from the lack of proper nonce validation in the wp_sliding_panel_user_options() function, which is responsible for handling user options within the plugin. Nonces in WordPress are security tokens used to verify that requests are intentional and originate from legitimate users. Without correct nonce checks, attackers can craft malicious requests that, when executed by an authenticated administrator (via clicking a link or visiting a crafted webpage), cause unauthorized changes to plugin settings. This attack vector requires no prior authentication by the attacker but does require user interaction from an administrator, making social engineering a key component. The vulnerability impacts the integrity of the plugin’s configuration but does not expose confidential data or affect system availability. The CVSS 3.1 base score of 4.3 reflects the medium severity, considering the ease of exploitation (network vector, low attack complexity), lack of required privileges, but necessity of user interaction. No public exploits have been reported yet, but the vulnerability is publicly disclosed and should be addressed promptly. The plugin is used in WordPress environments, which are widely deployed globally, making this a relevant concern for many organizations relying on this plugin for login/dashboard management.

Potential Impact

The primary impact of CVE-2025-5928 is the unauthorized modification of plugin settings, which can lead to altered authentication or dashboard behaviors. This may allow attackers to weaken security controls, disrupt administrative workflows, or introduce further attack vectors indirectly. While confidentiality and availability are not directly compromised, integrity loss can undermine trust in the affected WordPress site’s administrative functions. Organizations with high administrative activity or sensitive user data managed through this plugin face increased risk. Attackers leveraging this vulnerability could pivot to more damaging attacks if combined with other flaws or misconfigurations. The requirement for administrator interaction limits mass exploitation but targeted attacks against high-value sites remain a concern. The absence of known exploits currently reduces immediate risk but does not eliminate the threat, especially as the vulnerability is publicly documented.

Mitigation Recommendations

To mitigate CVE-2025-5928, organizations should first update the WP Sliding Login/Dashboard Panel plugin to a version that includes proper nonce validation once released by the vendor. In the absence of an official patch, administrators can implement manual nonce checks in the wp_sliding_panel_user_options() function by adding WordPress’s standard nonce verification functions (e.g., check_admin_referer). Additionally, restricting administrative access to trusted networks or VPNs can reduce exposure. Educating administrators about the risks of clicking untrusted links and employing web application firewalls (WAFs) to detect and block suspicious CSRF attempts can further reduce risk. Monitoring logs for unusual POST requests to the plugin’s endpoints may help detect exploitation attempts. Finally, limiting the number of users with administrative privileges and enforcing strong authentication mechanisms (e.g., MFA) can reduce the likelihood of successful exploitation.

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

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-06-09T14:40:09.201Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 684b8f23358c65714e6b579c

Added to database: 6/13/2025, 2:38:27 AM

Last enriched: 2/27/2026, 3:40:58 PM

Last updated: 3/22/2026, 11:12:09 PM

Views: 68

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