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-25152: Cross-Site Request Forgery (CSRF) in LukaszWiecek Smart DoFollow

0
Unknown
VulnerabilityCVE-2025-25152cvecve-2025-25152
Published: Fri Feb 07 2025 (02/07/2025, 10:11:57 UTC)
Source: CVE Database V5
Vendor/Project: LukaszWiecek
Product: Smart DoFollow

Description

Cross-Site Request Forgery (CSRF) vulnerability in LukaszWiecek Smart DoFollow smart-dofollow allows Stored XSS.This issue affects Smart DoFollow: from n/a through <= 1.0.2.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/01/2026, 22:03:20 UTC

Technical Analysis

CVE-2025-25152 identifies a Cross-Site Request Forgery (CSRF) vulnerability in the Smart DoFollow WordPress plugin developed by LukaszWiecek, affecting all versions up to and including 1.0.2. The vulnerability allows attackers to trick authenticated users into submitting unauthorized requests to the plugin, which can result in Stored Cross-Site Scripting (XSS). Stored XSS occurs when malicious scripts are permanently stored on the target server, for example, in plugin settings or database entries, and then executed in the context of other users' browsers. This combination of CSRF and Stored XSS is particularly dangerous because it leverages the victim's authenticated session to inject persistent malicious code, potentially compromising user accounts, stealing cookies, or performing actions with the victim's privileges. Exploitation requires the victim to be logged into a WordPress site using the vulnerable plugin and to visit a maliciously crafted webpage that triggers the CSRF attack. No public patches or exploit code are currently available, and no known active exploitation has been reported. The absence of a CVSS score suggests this is a newly disclosed vulnerability. The plugin's role in managing link attributes (DoFollow) means it is often used by site administrators, increasing the risk that an attacker could manipulate SEO-related settings or inject malicious content site-wide. The vulnerability highlights insufficient CSRF protections and input sanitization in the plugin's codebase.

Potential Impact

The impact of CVE-2025-25152 is significant for organizations using the Smart DoFollow plugin on WordPress sites. Successful exploitation can lead to persistent Stored XSS, which compromises the confidentiality and integrity of user data and site content. Attackers could hijack administrator sessions, inject malicious scripts that redirect users, steal sensitive cookies or credentials, and manipulate SEO settings to benefit malicious domains. This can damage organizational reputation, lead to data breaches, and facilitate further attacks such as phishing or malware distribution. Since the vulnerability requires an authenticated user, sites with multiple administrators or editors are at higher risk. The availability of the site may also be affected if injected scripts disrupt normal operations or cause browser crashes. Although no exploits are currently known in the wild, the combination of CSRF and Stored XSS makes this vulnerability attractive for attackers targeting WordPress sites globally, especially those relying on this plugin for SEO management.

Mitigation Recommendations

Organizations should immediately monitor for updates or patches from the plugin developer and apply them as soon as they become available. Until a patch is released, administrators should restrict access to the Smart DoFollow plugin settings to trusted users only and consider disabling the plugin if feasible. Implementing Web Application Firewall (WAF) rules to detect and block CSRF attempts and suspicious POST requests targeting the plugin endpoints can reduce risk. Site owners should enforce strict Content Security Policy (CSP) headers to limit the impact of potential XSS payloads. Regularly audit user privileges to minimize the number of users with administrative access. Additionally, security teams should review plugin code or use security scanners to identify and remediate missing CSRF tokens and improve input validation. Educating users about phishing and social engineering risks can help prevent victim interaction with malicious sites. Finally, maintain comprehensive backups to enable recovery if an attack occurs.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2025-02-03T13:35:19.028Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69cd7293e6bfc5ba1deeae8d

Added to database: 4/1/2026, 7:31:31 PM

Last enriched: 4/1/2026, 10:03:20 PM

Last updated: 4/6/2026, 9:26:46 AM

Views: 2

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 for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses