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-14354: CWE-352 Cross-Site Request Forgery (CSRF) in doubledome Resource Library for Logged In Users

0
Medium
VulnerabilityCVE-2025-14354cvecve-2025-14354cwe-352
Published: Fri Dec 12 2025 (12/12/2025, 03:20:48 UTC)
Source: CVE Database V5
Vendor/Project: doubledome
Product: Resource Library for Logged In Users

Description

The Resource Library for Logged In Users plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.4. This is due to missing nonce validation on multiple administrative functions. This makes it possible for unauthenticated attackers to perform various unauthorized actions including creating, editing, and deleting resources and categories via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

AI-Powered Analysis

AILast updated: 12/12/2025, 04:03:09 UTC

Technical Analysis

CVE-2025-14354 is a Cross-Site Request Forgery (CSRF) vulnerability identified in the 'Resource Library for Logged In Users' WordPress plugin developed by doubledome, affecting all versions up to and including 1.4. The vulnerability stems from the absence of nonce validation on several administrative functions within the plugin. Nonces in WordPress are security tokens used to verify that requests originate from legitimate users and not from malicious third-party sites. Without nonce validation, an attacker can craft a malicious request that, when executed by an authenticated administrator (e.g., by clicking a link), performs unauthorized actions such as creating, editing, or deleting resources and categories within the plugin. This type of attack compromises the integrity of the website content managed by the plugin but does not directly affect confidentiality or availability. The attack vector is remote and requires no prior authentication by the attacker, but it does require user interaction from an administrator. The vulnerability was published on December 12, 2025, with a CVSS v3.1 base score of 4.3, indicating a medium severity level. No public exploits have been reported to date. The lack of nonce validation is a common security oversight in WordPress plugin development, and this vulnerability highlights the importance of implementing standard security controls to prevent CSRF attacks. Organizations using this plugin should monitor for updates or patches from the vendor and consider interim mitigations to protect administrative interfaces.

Potential Impact

For European organizations, this vulnerability can lead to unauthorized modification or deletion of resources and categories managed by the affected WordPress plugin, potentially disrupting content management workflows and damaging data integrity. While the vulnerability does not directly expose sensitive data or cause denial of service, unauthorized content changes can undermine trust, cause operational disruptions, and may be leveraged as part of broader attack chains, such as defacement or phishing campaigns. Organizations with public-facing WordPress sites that rely on this plugin for resource management are particularly at risk. The requirement for administrator interaction means that social engineering or phishing campaigns targeting site administrators could facilitate exploitation. Given the widespread use of WordPress across Europe, especially in sectors like education, government, and SMEs, the vulnerability could impact a broad range of organizations. The medium severity rating suggests moderate risk, but the potential for integrity compromise warrants prompt attention.

Mitigation Recommendations

1. Monitor for and apply official patches or updates from the plugin vendor as soon as they become available. 2. In the absence of patches, implement manual nonce validation on all administrative functions within the plugin by modifying the plugin code or using security plugins that enforce nonce checks. 3. Restrict administrative access to trusted networks or VPNs to reduce exposure to CSRF attacks. 4. Educate WordPress administrators about the risks of clicking unsolicited links, especially those received via email or messaging platforms. 5. Employ web application firewalls (WAFs) with rules designed to detect and block CSRF attack patterns targeting WordPress administrative endpoints. 6. Regularly audit and monitor logs for suspicious administrative actions that could indicate exploitation attempts. 7. Consider disabling or replacing the plugin if timely patches are not forthcoming and the plugin is critical to operations.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-09T16:28:40.743Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 693b918b650da22753edbe51

Added to database: 12/12/2025, 3:52:43 AM

Last enriched: 12/12/2025, 4:03:09 AM

Last updated: 12/12/2025, 7:30:56 AM

Views: 9

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats