BrizyWordPress extension
CVE-2025-22763
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in NotFound Brizy Pro allows Reflected XSS. 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 confidenceReflected Cross-site Scripting (XSS) vulnerability in Brizy Pro plugin allows attackers to inject malicious JavaScript through unsanitized user input that gets reflected in web pages generated by the plugin. The vulnerability affects versions up to and including 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Check Brizy plugin versionIn WordPress admin, go to Plugins > Installed Plugins > Brizy. The version number is displayed under the plugin name. Alternatively, check the main plugin file (typically wp-content/plugins/brizy/brizy.php) for the 'Version' header in the plugin comment block.Affected if Version displayed is 2.6.1 or lower (any version up to and including 2.6.1).
-
Verify plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and confirm the Brizy plugin shows as 'Active' under its status.Affected if Plugin is active and running a vulnerable version.
-
Identify reflected input vectorsReview pages created with Brizy editor that accept user input through URL parameters (query strings) or form submissions. Check for any Brizy elements that display user-supplied data back to the page without apparent sanitization.Affected if Any Brizy-rendered page reflects URL parameters or form input directly into HTML output without encoding.
-
Test for XSS in Brizy-generated pagesUsing a browser or HTTP tool, submit a test payload such as <script>alert(1)</script> as a parameter value on a Brizy-rendered page. Inspect the page source or observe if the script executes upon page reload.Affected if The payload is reflected verbatim in the response HTML (visible in page source) rather than being HTML-encoded or removed.
You are affected if Brizy plugin version 2.6.1 or lower is installed and active, and any user-supplied input is reflected in Brizy-generated pages without proper sanitization or encoding.
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 proper input validation and output encoding for all user-supplied data before rendering in HTML context. Apply context-aware sanitization using established libraries like DOMPurify for any HTML content, and ensure all output is properly escaped based on its context.
Fix this in Brizy
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22763 — 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-22763 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