dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-8827

HIGH · 8.2 CVSS v4.0 Published 2026-05-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The AddressRepository::getSqlQuery() method constructs a database query without properly sanitizing user input, leading to SQL Injection. The method is not invoked anywhere within the extension itself and therefore poses no direct risk in a default installation. However, custom extensions that call this method with untrusted input would expose the site to SQL injection.

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 · high confidence

SQL injection vulnerability in AddressRepository::getSqlQuery() method due to unsanitized user input in constructed database queries. Not directly exploitable in default installation but becomes risky if custom extensions call this method with untrusted input.

MitigationSanitize all user input before using it in database queries within getSqlQuery(). Review custom extensions that may call this method and ensure any user-supplied data is properly parameterized or escaped.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the application version
    Locate the main application version file or check the framework version using the system's package manager or admin interface. Compare against any available version information from the vendor.
    Affected if Unable to determine version or running a version where custom extensions can call AddressRepository::getSqlQuery()
  2. Locate the AddressRepository class
    Search the codebase for the file containing the AddressRepository class, specifically the getSqlQuery() method. This is typically found in the repository or data access layer.
    Affected if The getSqlQuery() method exists and accepts parameters without sanitization
  3. Identify custom extensions
    Review the codebase for any custom or third-party extensions, plugins, or modules that extend or integrate with the core application. Check extension directories and configuration files.
    Affected if Custom extensions are installed that may invoke AddressRepository methods
  4. Inspect extension code for getSqlQuery usage
    Search all custom extension files for calls to AddressRepository::getSqlQuery() or similar repository methods. Examine the method calls to see if user-supplied parameters are passed directly.
    Affected if Extensions pass unvalidated user input directly to getSqlQuery() or similar repository query methods
  5. Review database query patterns
    Examine database query logs or profiler output to identify queries constructed using the AddressRepository. Look for dynamic SQL building without parameterized queries.
    Affected if Queries show string concatenation with user-supplied values being passed to repository methods
  6. Check for user input validation
    Trace the data flow from user-facing inputs (request parameters, form fields, API inputs) through to any repository method calls. Verify if input sanitization or parameterized queries are used.
    Affected if User input flows to AddressRepository methods without sanitization or parameterization

You are affected if custom extensions exist that pass untrusted user input to the AddressRepository::getSqlQuery() method without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Sanitize all user input before using it in database queries within getSqlQuery(). Review custom extensions that may call this method and ensure any user-supplied data is properly parameterized or escaped.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8827 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8827 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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