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-9626: CWE-352 Cross-Site Request Forgery (CSRF) in softwud Page Blocks

0
Medium
VulnerabilityCVE-2025-9626cvecve-2025-9626cwe-352
Published: Sat Oct 11 2025 (10/11/2025, 09:28:38 UTC)
Source: CVE Database V5
Vendor/Project: softwud
Product: Page Blocks

Description

The Page Blocks plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1.0. This is due to missing or incorrect nonce validation on the admin_process_widget_page_change function. This makes it possible for unauthenticated attackers to modify widget page block configurations via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/26/2026, 18:06:12 UTC

Technical Analysis

CVE-2025-9626 is a medium-severity vulnerability classified as CWE-352 (Cross-Site Request Forgery) found in the Page Blocks plugin for WordPress, developed by softwud. The vulnerability exists in all versions up to and including 1.1.0 due to missing or incorrect nonce validation in the admin_process_widget_page_change function. Nonces are security tokens used to verify that requests are intentional and originate from legitimate users. Without proper nonce validation, an attacker can craft a malicious request that, when executed by an authenticated administrator (via clicking a specially crafted link or visiting a malicious webpage), causes unauthorized modification of widget page block configurations. This attack vector requires no prior authentication but does require user interaction from an administrator, making it a targeted but feasible attack. The vulnerability affects the integrity of the website's widget configuration but does not impact confidentiality or availability. The CVSS v3.1 base score is 4.3, reflecting network attack vector, low attack complexity, no privileges required, user interaction required, unchanged scope, no confidentiality or availability impact, and low integrity impact. No patches or exploits are currently publicly available, but the vulnerability is published and should be addressed promptly to prevent potential misuse.

Potential Impact

The primary impact of this vulnerability is the unauthorized modification of widget page block configurations on WordPress sites using the vulnerable Page Blocks plugin. This can lead to defacement, insertion of malicious content, or disruption of site layout and functionality, potentially damaging the site's integrity and user trust. While confidentiality and availability are not directly affected, altered widgets could be used as a vector for further attacks, such as injecting malicious scripts or misleading users. Organizations relying on this plugin, especially those with high-privilege administrators who frequently manage site content, face increased risk of targeted attacks. The ease of exploitation (no authentication needed, only user interaction) increases the threat, particularly in environments where administrators may be susceptible to phishing or social engineering. The vulnerability could be leveraged in broader campaigns to compromise WordPress sites, which are widely used globally, potentially affecting e-commerce, media, and enterprise websites.

Mitigation Recommendations

To mitigate this vulnerability, organizations should first check for and apply any official patches or updates from the plugin vendor once available. In the absence of a patch, administrators should consider temporarily disabling the Page Blocks plugin or restricting its use to trusted administrators only. Implementing web application firewalls (WAFs) with custom rules to detect and block suspicious POST requests targeting widget configuration endpoints can reduce risk. Educate administrators on phishing and social engineering risks to minimize the chance of clicking malicious links. Additionally, site owners can implement Content Security Policy (CSP) headers to limit the impact of injected content and monitor logs for unusual administrative actions. Regular backups of site configurations will help restore integrity if unauthorized changes occur. Finally, plugin developers should be encouraged to adopt proper nonce validation and security best practices in future releases.

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

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-08-28T19:19:01.503Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68ea263e5baaa01f1ca0fffd

Added to database: 10/11/2025, 9:41:18 AM

Last enriched: 2/26/2026, 6:06:12 PM

Last updated: 3/25/2026, 5:58:32 AM

Views: 53

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