dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-36670

HIGH · 8.8 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
A Time-Based Blind SQL Injection vulnerability in the alias_management module of OpenSIPS Control Panel (opensips-cp) prior to version 9.3.3 allows authenticated attackers to execute arbitrary SQL commands via the 'table' GET parameter in alias_management.php.

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

A time-based blind SQL injection vulnerability exists in the alias_management module of OpenSIPS Control Panel. The 'table' GET parameter in alias_management.php is not properly sanitized, allowing authenticated attackers to inject and execute arbitrary SQL commands. Since it's blind SQLi, attackers infer results through time-based response delays.

MitigationUpgrade to OpenSIPS Control Panel version 9.3.3 or later to obtain the patch. Additionally, review user access controls and implement parameterized queries for all database interactions in the affected module.

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
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 checks

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

  1. Locate OpenSIPS Control Panel installation
    Search for the file 'alias_management.php' in your web server's document root or common OpenSIPS directories (e.g., /var/www/html/opensips-cp, /usr/share/opensips-cp, or similar). Also check for the presence of the main OpenSIPS Control Panel files like 'config.php' or 'index.php'.
    Affected if OpenSIPS Control Panel is installed on this server.
  2. Determine installed OpenSIPS Control Panel version
    Open the 'CHANGELOG' or 'VERSION' file in the OpenSIPS Control Panel root directory. Alternatively, check the header comments in the main 'index.php' file for a version string. Compare the version number to the fixed version 9.3.3.
    Affected if The installed version is lower than 9.3.3.
  3. Verify alias_management module is present
    Check for the existence of the file 'alias_management.php' within the 'tools' subdirectory of your OpenSIPS Control Panel installation (typically at alias_management/alias_management.php).
    Affected if The alias_management.php file exists in the installation.
  4. Confirm the vulnerable parameter is in use
    Examine the source code of alias_management.php and locate the handling of the 'table' GET parameter. Search for code that directly incorporates this parameter into SQL queries without using prepared statements or proper escaping.
    Affected if The code directly uses the 'table' GET parameter in SQL queries without parameterized queries or sanitization.
  5. Check authentication status
    Review the authentication mechanism in alias_management.php. Determine whether the page enforces user authentication before allowing access to the alias management functionality.
    Affected if The module is accessible without proper authentication or authentication can be bypassed.

A user is affected if OpenSIPS Control Panel version is below 9.3.3, the alias_management.php module exists, and the 'table' GET parameter is handled in SQL queries without prepared statements.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to OpenSIPS Control Panel version 9.3.3 or later to obtain the patch. Additionally, review user access controls and implement parameterized queries for all database interactions in the affected module.

Recommended fix Moderate confidence

OpenSIPS Control Panel 9.3.3 or later

  1. Verify current OpenSIPS Control Panel version by checking the web interface or running 'git describe --tags' in the installation directory
  2. Backup the entire OpenSIPS Control Panel installation directory and database before proceeding
  3. Download OpenSIPS Control Panel version 9.3.3 or later from the official GitHub repository (https://github.com/opensips/opensips-control-panel)
  4. Extract the new version and replace the existing files, preserving local configuration files such as config.php
  5. Verify the alias_management.php file has been updated and contains the fix for the 'table' parameter handling
  6. Test the application functionality, particularly the alias_management module, to ensure the upgrade was successful
  7. Review access logs to confirm no exploitation occurred prior to patching

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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