dbcve.org
InjectionWeakness · CWE-74

CVE-2026-15482

HIGH · 7.3 CVSS v3.1 Published 2026-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click 5 weeks old

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
A weakness has been identified in Aster Telecom Azcall 10/11. This issue affects some unknown processing of the file /azcall/adm/gestao_loja/sis.php?t=consultar of the component HTTP Handler. Executing a manipulation of the argument nome/perfil/status can lead to sql injection. The attack may be performed from remote. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

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 Aster Telecom Azcall 10/11 allows remote attackers to inject malicious SQL queries via the nome, perfil, or status parameters in /azcall/adm/gestao_loja/sis.php?t=consultar. The HTTP Handler component fails to properly sanitize user input before using it in database queries, enabling unauthenticated attackers to manipulate SQL statements.

MitigationImplement parameterized queries or prepared statements for all database operations using user-supplied input. As an interim control, deploy a Web Application Firewall (WAF) to filter SQL injection attempts until proper code fixes can be applied.

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checks

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

  1. Identify if Aster Telecom Azcall is installed
    Search the web server document root for the /azcall directory or look for files containing 'azcall' in the application path. Common locations include /var/www/html/azcall or C:\inetpub\wwwroot\azcall.
    Affected if The /azcall directory exists on the server and contains application files.
  2. Determine the installed Azcall version
    Check for version files or headers within the /azcall directory. Look for version information in the application's main index file, an about page, or configuration files. Compare the found version against versions 10 and 11.
    Affected if The installed version is either 10 or 11.
  3. Verify the vulnerable script exists
    Check if the file /azcall/adm/gestao_loja/sis.php exists on the server by attempting to access it via HTTP request to the affected endpoint: GET /azcall/adm/gestao_loja/sis.php?t=consultar
    Affected if The script /azcall/adm/gestao_loja/sis.php is present and accessible via the web.
  4. Confirm the application processes the vulnerable parameters
    Send a test HTTP request to the affected endpoint with the parameters nome, perfil, or status included. For example: GET /azcall/adm/gestao_loja/sis.php?t=consultar&nome=test
    Affected if The application accepts and processes input via the nome, perfil, or status parameters without apparent sanitization.
  5. Inspect database query handling in the affected script
    If code access is available, review /azcall/adm/gestao_loja/sis.php to verify whether user-supplied input from nome, perfil, or status parameters is directly concatenated into SQL queries without using prepared statements or parameterization.
    Affected if The code directly incorporates the affected parameters into SQL queries without sanitization or prepared statements.

A user is affected if Aster Telecom Azcall versions 10 or 11 is installed, the vulnerable /azcall/adm/gestao_loja/sis.php script exists, and the application accepts input via the nome, perfil, or status parameters without SQL 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

Implement parameterized queries or prepared statements for all database operations using user-supplied input. As an interim control, deploy a Web Application Firewall (WAF) to filter SQL injection attempts until proper code fixes can be applied.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15482 — 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-15482 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