dbcve.org
ProntuscmsApplication · Altavoz

CVE-2019-15503

CRITICAL · 9.8 CVSS v3.0 Published 2019-08-26
Fix available
A fix is available. Upgrade to after 12.0.3.0 or later.
See remediation →
100/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
cgi-cpn/xcoding/prontus_videocut.cgi in AltaVoz Prontus (aka ProntusCMS) through 12.0.3.0 has "Improper Neutralization of Special Elements used in an OS Command," allowing attackers to execute OS commands via an HTTP GET parameter.

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 confidence

OS command injection vulnerability in ProntusCMS's prontus_videocut.cgi script allows remote attackers to execute arbitrary operating system commands via unsanitized HTTP GET parameters. The lack of proper input validation on user-supplied data enables attackers to inject shell metacharacters into OS-level commands.

MitigationUpgrade to ProntusCMS version 12.0.3.1 or later which contains the security patch. If upgrade is not immediately feasible, disable the vulnerable CGI script or implement strict input validation and whitelist filtering on all parameter inputs before passing to system calls.

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
ProntuscmsApplication
Affected:<= 12.0.3.0

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.0/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. Verify ProntusCMS is installed
    Look for ProntusCMS installation directories on the server. Common locations include /var/www/html/, /home/*/www/, or custom web root directories. Search for files named prontus_videocut.cgi or directories containing 'prontus' in the name.
    Affected if ProntusCMS is present on the system
  2. Check installed ProntusCMS version
    Locate the ProntusCMS version file or check the admin interface for the version number. Version information is typically found in a config file, about page, or version file within the ProntusCMS installation directory.
    Affected if The installed version is 12.0.3.0 or earlier (any version <= 12.0.3.0)
  3. Confirm prontus_videocut.cgi exists
    Search for the file prontus_videocut.cgi within the ProntusCMS installation directory, typically under the cgi-bin/ or a similar CGI scripts folder.
    Affected if The file prontus_videocut.cgi exists in the ProntusCMS installation
  4. Verify CGI script is web-accessible
    Check the web server configuration to confirm that CGI scripts are enabled and that prontus_videocut.cgi is accessible via HTTP requests (not blocked by .htaccess rules or similar access controls). Attempt a HEAD request to the script URL if permissible.
    Affected if CGI execution is enabled and the script is reachable over the network
  5. Check for command injection exposure
    Review the prontus_videocut.cgi script source code to confirm it processes HTTP GET parameters without proper sanitization and passes user input to system calls (functions like exec, system, or shell backticks).
    Affected if The script contains unsafe system calls using unsanitized HTTP GET parameters

A user is affected if ProntusCMS version 12.0.3.0 or earlier is installed AND the prontus_videocut.cgi script exists and is web-accessible, as this enables remote command injection via unsanitized HTTP GET parameters.

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
Upgrade available Upgrade to a release after 12.0.3.0
Interim mitigation

Upgrade to ProntusCMS version 12.0.3.1 or later which contains the security patch. If upgrade is not immediately feasible, disable the vulnerable CGI script or implement strict input validation and whitelist filtering on all parameter inputs before passing to system calls.

Fix this in Prontuscms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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