BrizyWordPress extension
CVE-2025-26902
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in Brizy Brizy Pro allows Cross Site Request Forgery.This issue affects Brizy Pro: from n/a through 2.6.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the Brizy Pro WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions such as modifying plugin settings, creating content, or changing user permissions without their explicit consent.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
BrizyWordPress extension
<= 2.6.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Brizy plugin versionNavigate to WordPress admin > Plugins > Installed Plugins, locate 'Brizy' or 'Brizy Pro', and note the version number displayedAffected if The displayed version number is 2.6.1 or lower
-
Verify plugin statusConfirm the Brizy plugin is currently activated on the WordPress siteAffected if The plugin shows as 'Active' status in the Plugins list
-
Check plugin for CSRF token implementation in formsInspect the plugin's PHP files in wp-content/plugins/brizy/ for form handling code. Look for presence of wp_nonce_field(), wp_verify_nonce(), or similar nonce verification functions in files handling form submissionsAffected if Form-handling files lack nonce verification or token validation logic for state-changing operations
-
Inspect AJAX endpoints for CSRF protectionExamine AJAX action handlers in the plugin for nonce verification. Check if admin-ajax.php calls from Brizy include a valid nonce parameter and validate it before processing requestsAffected if AJAX endpoints process requests without verifying nonce tokens or validating Origin/Referer headers
-
Review state-changing operationsIdentify plugin files that modify settings, create content, or change user permissions. Verify these operations check for CSRF protection tokensAffected if Code that alters plugin settings, creates content, or modifies permissions does not validate anti-CSRF tokens
You are affected if the Brizy plugin version is 2.6.1 or lower and the plugin is active, with state-changing operations lacking nonce or header validation for CSRF protection.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations including form submissions and AJAX endpoints, and validate Origin/Referer headers to ensure requests originate from trusted sources.
Fix this in Brizy
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26902 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-26902 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data