Skip to main content
DashboardThreatsMapFeedsAPI
reconnecting
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-10309: CWE-352 Cross-Site Request Forgery (CSRF) in bsmye PayPal Forms

0
Medium
VulnerabilityCVE-2025-10309cvecve-2025-10309cwe-352
Published: Fri Oct 03 2025 (10/03/2025, 11:17:15 UTC)
Source: CVE Database V5
Vendor/Project: bsmye
Product: PayPal Forms

Description

The PayPal Forms plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.3. This is due to missing nonce validation on the form creation and management functions. This makes it possible for unauthenticated attackers to create new PayPal forms and modify PayPal payment 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

AILast updated: 10/03/2025, 11:33:33 UTC

Technical Analysis

CVE-2025-10309 is a Cross-Site Request Forgery (CSRF) vulnerability affecting the PayPal Forms plugin for WordPress, developed by bsmye. This vulnerability exists in all versions up to and including 1.0.3. The root cause is the absence of nonce validation on critical form creation and management functions within the plugin. Nonce validation is a security mechanism used in WordPress to ensure that requests made to perform sensitive actions originate from legitimate users and not from forged requests. Due to this missing validation, an unauthenticated attacker can craft malicious requests that, when executed by an authenticated site administrator (for example, by clicking a specially crafted link), allow the attacker to create new PayPal payment forms or modify existing PayPal payment settings on the affected WordPress site. This can lead to unauthorized manipulation of payment configurations, potentially redirecting payments or causing financial fraud. The vulnerability requires user interaction (the administrator must be tricked into clicking a malicious link), but does not require the attacker to have any privileges or authentication on the target site. The CVSS v3.1 base score is 4.3 (medium severity), reflecting the limited impact on confidentiality and availability but a low impact on integrity due to the ability to modify payment settings. No known exploits are currently reported in the wild, and no patches have been linked yet, indicating that mitigation may require manual intervention or updates once available.

Potential Impact

For European organizations using WordPress sites with the bsmye PayPal Forms plugin, this vulnerability poses a risk of unauthorized modification of payment forms and settings. This could lead to financial fraud, misdirection of payments, or disruption of e-commerce operations. Organizations handling significant online transactions, especially SMEs and e-commerce platforms relying on PayPal integration, could face financial losses and reputational damage. Since the attack requires tricking an administrator, organizations with less stringent user awareness or lacking multi-factor authentication for admin accounts are more vulnerable. Additionally, regulatory compliance under GDPR may be impacted if financial data integrity is compromised, potentially leading to legal consequences. The vulnerability does not directly expose customer data but undermines payment process integrity, which is critical for trust and operational continuity.

Mitigation Recommendations

1. Immediate mitigation involves educating WordPress site administrators about the risk of clicking unsolicited or suspicious links, especially those that could trigger administrative actions. 2. Restrict administrative access to trusted networks or use VPNs to reduce exposure to CSRF attacks. 3. Implement multi-factor authentication (MFA) for all WordPress admin accounts to reduce the risk of unauthorized actions even if an admin is tricked. 4. Monitor WordPress logs for unusual creation or modification of PayPal forms and payment settings. 5. Until an official patch is released, consider disabling or removing the PayPal Forms plugin if feasible. 6. Once available, promptly apply updates that add nonce validation or other CSRF protections. 7. Employ web application firewalls (WAFs) with rules to detect and block CSRF attack patterns targeting WordPress admin endpoints. 8. Regularly audit plugin usage and permissions to ensure minimal attack surface.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-09-11T22:49:58.682Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68dfb274c3835a5fbe033bd9

Added to database: 10/3/2025, 11:24:36 AM

Last enriched: 10/3/2025, 11:33:33 AM

Last updated: 10/7/2025, 4:27:45 AM

Views: 17

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 are available only with a Pro account. Contact root@offseq.com for access.

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