dbcve.org
AstppApplication · Inextrix

CVE-2020-37153

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
ASTPP 4.0.1 contains multiple vulnerabilities including cross-site scripting and command injection in SIP device configuration and plugin management interfaces. Attackers can exploit these flaws to inject system commands, hijack administrator sessions, and potentially execute arbitrary code with root permissions through cron task manipulation.

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

ASTPP 4.0.1 contains multiple critical vulnerabilities in its SIP device configuration and plugin management interfaces. Attackers can exploit cross-site scripting (XSS) flaws to hijack administrator sessions and command injection vulnerabilities to execute system commands with root privileges through manipulation of cron tasks.

MitigationImplement strict input validation and output encoding for all user-supplied data in SIP configuration and plugin interfaces; sanitize command execution contexts and restrict cron task permissions to prevent privilege escalation.

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
AstppApplication
Affected:= 4.0.1

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm ASTPP installation and version
    Locate the ASTPP installation directory and check the version file, typically found in /var/www/htmlASTPP or similar web root paths. Common version files include VERSION, version.php, or check the package manager if installed via apt/yum.
    Affected if The installed version is 4.0.1
  2. Identify web server configuration for ASTPP
    Check the web server (Apache/Nginx) configuration for ASTPP virtual hosts or check if the application is accessible via HTTP/HTTPS. Look for configuration files in /etc/apache2/sites-enabled/ or /etc/nginx/sites-enabled/.
    Affected if ASTPP is serving web content and the version is 4.0.1
  3. Verify SIP device configuration interface exposure
    Access the SIP device configuration interface in the ASTPP admin panel. Typically found under Devices or SIP menu items in the administrative web interface. Attempt to locate the endpoint handling SIP device parameters.
    Affected if The SIP configuration interface is accessible and the application version is 4.0.1
  4. Check plugin management interface accessibility
    Navigate to the plugin management section of the ASTPP administrative interface, typically found under Plugins or Add-ons menu. Identify the endpoints that handle plugin installation and configuration.
    Affected if The plugin management interface is accessible and the application version is 4.0.1
  5. Inspect cron task configuration for suspicious entries
    Examine system cron files and ASTPP-specific cron configurations. Check /etc/crontab, /var/spool/cron/, and any ASTPP cron configuration files in the installation directory for unexpected or user-added cron tasks.
    Affected if Unexpected cron entries exist, particularly those executing shell commands or scripts with elevated privileges, in a 4.0.1 installation

A system is affected if it is running Inextrix Astpp version 4.0.1 with accessible SIP device configuration or plugin management web interfaces, or if unauthorized cron tasks are present on the system.

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

Implement strict input validation and output encoding for all user-supplied data in SIP configuration and plugin interfaces; sanitize command execution contexts and restrict cron task permissions to prevent privilege escalation.

Recommended fix Moderate confidence

ASTPP version > 4.0.2 (check official release notes for exact fixed version)

  1. 1. Back up the entire ASTPP installation directory and database before attempting any upgrade
  2. 2. Review the official ASTPP changelog or release notes at www.astppbilling.org to identify the fixed release version
  3. 3. Download the confirmed fixed version of ASTPP from the official repository
  4. 4. Test the upgrade in a non-production environment first
  5. 5. Execute the upgrade process following official documentation
  6. 6. Verify that the SIP device configuration and plugin management interfaces are functioning correctly post-upgrade
  7. 7. Validate that the XSS and command injection vulnerabilities are no longer present
  8. 8. Review cron tasks to ensure no unauthorized root-level commands were added
Caveat Review migration guide for changes between 4.0.1 and the target version, as configuration or database schema changes may occur

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

Fix this in Astpp Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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