CVE-2026-27087
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 G5Theme Wolverine Framework wolverine-framework allows Reflected XSS.This issue affects Wolverine Framework: from n/a through <= 1.9.
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 XSS vulnerability in G5Theme's Wolverine Framework allows attackers to inject malicious JavaScript through unsanitized user inputs that get reflected in web pages without proper output encoding, enabling session hijacking or credential theft.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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 Wolverine Framework installationSearch your codebase or dependencies for 'Wolverine Framework', 'g5-wolverine', or related G5Theme package references. Check package.json, composer.json, or framework configuration files for the framework name.Affected if Wolverine Framework from G5Theme is present in the environment
-
Locate user input handling codeSearch source files for request parameter retrieval (e.g., $_GET, $_POST, request.params, request.query) that are then output directly to HTML templates or responses without visible encoding functions.Affected if User-supplied parameters are retrieved and rendered without evident sanitization or encoding
-
Check template files for unencoded outputInspect template files (.twig, .php, .jsp, .html) for variables outputting request data using syntax like {{variable}} or <%=variable%> without context-aware encoding functions such as htmlspecialchars(), escape(), or similar.Affected if Templates render user input directly without applying output encoding
-
Test for reflected XSS manuallySubmit a harmless test payload like <script>alert('XSS')</script> or <img src=x onerror=alert('XSS')> as a query parameter or form input to your application's endpoints, then inspect the response HTML to see if the payload is rendered as-is.Affected if The test payload executes or appears unescaped in the response page
A user is affected if G5Theme's Wolverine Framework is in use AND user-provided input is reflected in web pages without output encoding, allowing the XSS payload to render unescaped in the browser.
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 context-aware output encoding and input validation/sanitization across all user-controlled input points in the web application.
- 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-2026-27087 — 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-2026-27087 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