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-13629: CWE-352 Cross-Site Request Forgery (CSRF) in xbenx WP Landing Page

0
Medium
VulnerabilityCVE-2025-13629cvecve-2025-13629cwe-352
Published: Sat Dec 06 2025 (12/06/2025, 05:49:26 UTC)
Source: CVE Database V5
Vendor/Project: xbenx
Product: WP Landing Page

Description

The WP Landing Page plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 0.9.3. This is due to missing nonce validation on the 'wplp_api_update_text' function. This makes it possible for unauthenticated attackers to update arbitrary post meta 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/13/2025, 07:09:34 UTC

Technical Analysis

CVE-2025-13629 is a Cross-Site Request Forgery (CSRF) vulnerability identified in the WP Landing Page plugin for WordPress, affecting all versions up to and including 0.9.3. The vulnerability stems from the absence of nonce validation in the 'wplp_api_update_text' function, which is responsible for updating post meta data. Nonce tokens are security measures used in WordPress to verify that requests originate from legitimate users and not from malicious third parties. Without this validation, an attacker can craft a malicious request that, if an authenticated site administrator is tricked into clicking (for example, via a phishing email or malicious website), will execute arbitrary updates to post meta data on the affected site. This can lead to unauthorized content changes, potentially defacing the site or injecting misleading information. The vulnerability requires no prior authentication (AV:N), has low attack complexity (AC:L), requires no privileges (PR:N), but does require user interaction (UI:R). The scope is unchanged (S:U), and the impact affects integrity (I:L) but not confidentiality or availability. The CVSS v3.1 base score is 4.3, categorizing it as medium severity. No patches or exploits are currently documented, but the risk remains significant due to the potential for social engineering to trigger the attack. The vulnerability is particularly relevant for websites relying on the WP Landing Page plugin for content management and landing page customization.

Potential Impact

For European organizations, the primary impact of this vulnerability is the potential unauthorized modification of website content, which can undermine the integrity and trustworthiness of their online presence. This can affect brand reputation, customer trust, and potentially lead to misinformation or fraudulent content being displayed. While the vulnerability does not directly compromise sensitive data confidentiality or site availability, the integrity breach can be exploited for phishing campaigns, misinformation, or to facilitate further attacks. Organizations in sectors such as e-commerce, media, and public services that rely heavily on WordPress and the WP Landing Page plugin are at higher risk. The need for administrator interaction means that social engineering defenses are critical. Additionally, regulatory frameworks like GDPR emphasize the importance of maintaining data integrity and security, so failure to address this vulnerability could have compliance implications if it leads to data manipulation or customer deception.

Mitigation Recommendations

To mitigate CVE-2025-13629, European organizations should: 1) Monitor for and apply any official patches or updates from the WP Landing Page plugin vendor as soon as they become available. 2) If patches are not yet available, implement custom nonce validation in the 'wplp_api_update_text' function or disable the vulnerable functionality temporarily. 3) Educate WordPress site administrators about the risks of phishing and social engineering attacks, emphasizing caution when clicking links from untrusted sources. 4) Employ web application firewalls (WAFs) with rules to detect and block suspicious CSRF attempts targeting the plugin’s API endpoints. 5) Regularly audit and monitor website content and post meta data for unauthorized changes to detect exploitation early. 6) Limit administrator access and use multi-factor authentication (MFA) to reduce the risk of compromised credentials facilitating exploitation. 7) Review and harden overall WordPress security posture, including plugin management and user privilege controls.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-11-24T21:40:10.616Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6933c71e11163305efef3dd5

Added to database: 12/6/2025, 6:03:10 AM

Last enriched: 12/13/2025, 7:09:34 AM

Last updated: 2/4/2026, 2:39:16 PM

Views: 44

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