BrizyWordPress extension
CVE-2025-26901
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 · uneditedMissing Authorization vulnerability in Brizy Brizy Pro allows Exploiting Incorrectly Configured Access Control Security Levels.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 confidenceBrizy Pro plugin for WordPress contains a missing authorization vulnerability where the plugin fails to properly enforce access control checks on certain functionality. This allows attackers to exploit incorrectly configured access control security levels to perform actions they should not be permitted to perform. The vulnerability affects versions through 2.6.1.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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.
-
Verify the installed Brizy plugin versionNavigate to WordPress admin > Plugins > Installed Plugins > Brizy Pro and note the version number displayed. Alternatively, check the plugin header in the main plugin file (typically in wp-content/plugins/brizy-pro/main.php).Affected if The displayed version is 2.6.1 or any lower version number.
-
Identify accessible Brizy AJAX endpointsCheck your web server access logs for POST requests to /wp-admin/admin-ajax.php with Brizy-related action parameters (such as 'brizy_upload', 'brizy_save', 'brizy_get', or similar Brizy-specific action values).Affected if AJAX endpoints respond without requiring proper authentication or capability verification.
-
Review WordPress user roles with Brizy accessIn WordPress admin, go to Users > All Users and identify which user accounts have access to the Brizy editor or builder functionality. Check if low-privileged users (such as Subscribers or Contributors) can access Brizy editing features.Affected if Users with low-level roles (Subscriber, Contributor) can access or modify Brizy content that should require Editor or Administrator privileges.
-
Inspect Brizy plugin file permissionsExamine the Brizy Pro plugin files, particularly AJAX handlers in the includes or endpoints directories, to verify that access control functions (such as current_user_can or check_ajax_referer) are properly called before processing requests.Affected if AJAX or action handlers in Brizy do not invoke capability checks before executing sensitive operations.
A user is affected if the installed Brizy Pro version is 2.6.1 or lower AND low-privileged users can access or modify content without proper authorization checks.
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 dataUpdate Brizy Pro to the latest version which should contain proper authorization controls. If no update is available, restrict access to affected endpoints at the server level and audit user capabilities.
Fix this in Brizy
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26901 — 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-26901 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