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-67593: Cross-Site Request Forgery (CSRF) in Stiofan UsersWP

0
Medium
VulnerabilityCVE-2025-67593cvecve-2025-67593
Published: Tue Dec 09 2025 (12/09/2025, 14:14:17 UTC)
Source: CVE Database V5
Vendor/Project: Stiofan
Product: UsersWP

Description

Cross-Site Request Forgery (CSRF) vulnerability in Stiofan UsersWP userswp allows Cross Site Request Forgery.This issue affects UsersWP: from n/a through <= 1.2.48.

AI-Powered Analysis

AILast updated: 12/09/2025, 14:51:48 UTC

Technical Analysis

CVE-2025-67593 identifies a Cross-Site Request Forgery (CSRF) vulnerability in the UsersWP plugin developed by Stiofan, affecting all versions up to 1.2.48. CSRF vulnerabilities allow attackers to induce authenticated users to execute unwanted actions on a web application in which they are currently authenticated. In this case, the vulnerability resides in the UsersWP plugin, which is commonly used to manage user profiles and registration on WordPress sites. An attacker could craft a malicious web page or link that, when visited by an authenticated user of a vulnerable WordPress site, triggers unauthorized actions such as changing user details or performing administrative functions without the user's consent. The vulnerability does not require the attacker to have direct access to the victim's credentials but relies on the victim being logged in and visiting a malicious site. There are no known public exploits or patches available at the time of disclosure, and no CVSS score has been assigned. The absence of anti-CSRF tokens or improper validation of request origins likely contributes to this vulnerability. The impact primarily affects the integrity of user data and could potentially disrupt availability if critical user management functions are manipulated. Since the plugin is widely used in WordPress environments, the scope of affected systems is significant, especially for organizations relying on this plugin for user management. The vulnerability requires the victim to be authenticated but does not require additional user interaction beyond visiting a malicious link or page. This makes exploitation feasible but somewhat limited to targeted attacks. The vulnerability is classified as published and reserved under Patchstack's assigner but lacks detailed technical mitigations or patches at present.

Potential Impact

For European organizations, this CSRF vulnerability poses risks to the integrity and availability of user management functions within WordPress sites using the UsersWP plugin. Attackers could manipulate user profiles, escalate privileges, or disrupt user services, potentially leading to unauthorized access or denial of service conditions. This could affect customer trust, compliance with data protection regulations such as GDPR, and operational continuity. Organizations in sectors with high reliance on web-based user management, including e-commerce, education, and public services, may face increased risk. The lack of known exploits reduces immediate threat but does not eliminate the risk of targeted attacks. The vulnerability could also be leveraged as part of a broader attack chain to gain further access or disrupt services. Given the widespread use of WordPress and the plugin, the potential impact is moderate but could escalate if combined with other vulnerabilities or social engineering tactics.

Mitigation Recommendations

Organizations should immediately inventory their WordPress installations to identify the presence and version of the UsersWP plugin. Until an official patch is released, administrators should consider disabling or restricting the plugin's user management features to trusted users only. Implementing web application firewalls (WAFs) with rules to detect and block CSRF attack patterns can provide interim protection. Enforcing strict Content Security Policy (CSP) headers and SameSite cookie attributes can reduce the risk of CSRF exploitation. Additionally, reviewing and tightening user roles and permissions within WordPress can limit the potential damage from exploited CSRF actions. Monitoring user activity logs for unusual changes or access patterns is recommended. Once patches are available, prompt application is critical. Educating users about the risks of clicking unknown links while authenticated can also reduce exposure. Finally, developers should ensure that all forms and state-changing requests include anti-CSRF tokens and validate request origins.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2025-12-09T12:21:39.681Z
Cvss Version
null
State
PUBLISHED

Threat ID: 693833ae29cea75c35ae5770

Added to database: 12/9/2025, 2:35:26 PM

Last enriched: 12/9/2025, 2:51:48 PM

Last updated: 12/10/2025, 9:05:05 PM

Views: 4

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