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/19/2025, 05:11:51 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. This plugin, used to manage resources and categories accessible to logged-in users, lacks proper nonce validation on multiple administrative functions in all versions up to and including 1.4. Nonce validation is a security mechanism designed to ensure that requests made to a web application are intentional and originate from legitimate users. The absence of this validation allows an attacker to craft malicious requests that, when executed by an authenticated administrator (via clicking a malicious link or visiting a crafted webpage), can perform unauthorized actions such as creating, editing, or deleting resources and categories within the plugin. This type of attack does not require the attacker to be authenticated themselves but relies on social engineering to trick an authenticated user. The vulnerability impacts the integrity of the affected WordPress sites by enabling unauthorized modifications but does not directly affect confidentiality or availability. The CVSS v3.1 base score is 4.3 (medium), with the vector indicating network attack vector, low attack complexity, no privileges required, user interaction required, and unchanged scope. No patches or exploit code are currently publicly available, but the vulnerability is published and should be addressed promptly to prevent potential exploitation.

Potential Impact

For European organizations, this vulnerability can lead to unauthorized modification of website content managed via the affected plugin, potentially undermining the integrity of publicly accessible resources or internal documentation. Attackers could manipulate resource listings, inject misleading or malicious content, or disrupt organizational workflows that rely on the plugin. While confidentiality and availability impacts are minimal, the integrity compromise could damage organizational reputation, cause misinformation, or facilitate further attacks if attackers insert malicious links or content. Organizations with public-facing WordPress sites using this plugin are at higher risk, especially those with administrators who may be targeted via phishing or social engineering. The lack of known exploits reduces immediate risk but does not eliminate the threat, as attackers could develop exploits. The impact is more pronounced in sectors relying heavily on WordPress for content management, including education, government, and SMEs across Europe.

Mitigation Recommendations

To mitigate this vulnerability, European organizations should first verify if they use the 'Resource Library for Logged In Users' plugin and identify the version in use. Immediate steps include: 1) Updating the plugin to a patched version once released by the vendor; if no patch is available, consider temporarily disabling the plugin to prevent exploitation. 2) Implementing web application firewalls (WAFs) with rules to detect and block suspicious CSRF attempts targeting the plugin's administrative endpoints. 3) Educating administrators about the risks of clicking on unsolicited links, especially when logged into WordPress admin panels. 4) Enforcing multi-factor authentication (MFA) for WordPress admin accounts to reduce the risk of account compromise. 5) Monitoring logs for unusual administrative actions or changes to resources and categories. 6) Employing Content Security Policy (CSP) headers to limit the impact of malicious scripts. These steps go beyond generic advice by focusing on plugin-specific controls and user awareness tailored to the nature of this CSRF vulnerability.

Need more detailed analysis?Upgrade to Pro Console

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/19/2025, 5:11:51 AM

Last updated: 2/7/2026, 7:45:01 AM

Views: 106

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