dbcve.org
Goadmin CeApplication · Goautodial

CVE-2015-2845

HIGH · 10.0 CVSS v2.0 Published 2015-05-12
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
High EPSS 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
The cpanel function in go_site.php in GoAutoDial GoAdmin CE before 3.3-1421902800 allows remote attackers to execute arbitrary commands via the $type portion of the PATH_INFO.

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

Command injection vulnerability in GoAutoDial GoAdmin CE's go_site.php cpanel function. The $type parameter from PATH_INFO is directly used in a system call without sanitization, allowing remote attackers to execute arbitrary OS commands.

MitigationUpdate to GoAutoDial GoAdmin CE version 3.3-1421902800 or later. Alternatively, implement strict input validation/sanitization on the $type PATH_INFO parameter before using it in any 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
Goadmin CeApplication
Affected:= 3.0= 3.3

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 GoAutoDial GoAdmin CE installation
    Look for the GoAutoDial web interface or check for /var/www/html/go_site.php or similar web root paths. The application is typically installed on CentOS/RHEL servers running the GoAutoDial telephony suite.
    Affected if GoAutoDial GoAdmin CE is installed on the system
  2. Determine the GoAdmin CE version
    Check the version file or the go_site.php header comments. Common locations include /var/www/html/go_site.php or the GoAdmin application directory. Look for version strings like '3.0' or '3.3' in the source code.
    Affected if The installed version is 3.0 or 3.3
  3. Locate the vulnerable go_site.php file
    Find the go_site.php file in the web root. The vulnerability exists in the cpanel function where the $type parameter from PATH_INFO is used directly in system() calls without sanitization.
    Affected if The go_site.php file exists and contains the cpanel function with the $type parameter handling
  4. Verify the PATH_INFO parameter handling
    Examine the go_site.php source code around the cpanel function. Look for system(), exec(), or shell_exec() calls that incorporate the $type PATH_INFO parameter without sanitization (no escapeshellarg or similar).
    Affected if The code uses the $type parameter from PATH_INFO directly in system calls without input validation

The system is affected if GoAutoDial GoAdmin CE versions 3.0 or 3.3 are installed with the go_site.php file present and the cpanel function uses the $type PATH_INFO parameter in unsanitized system calls.

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

Update to GoAutoDial GoAdmin CE version 3.3-1421902800 or later. Alternatively, implement strict input validation/sanitization on the $type PATH_INFO parameter before using it in any system calls.

Recommended fix High confidence

GoAdmin CE 3.3-1421902800 or later

  1. Backup the current GoAdmin CE installation and database before proceeding with the upgrade
  2. Download GoAdmin CE version 3.3-1421902800 or a later stable release from the official GoAutoDial repository (goautodial.org)
  3. Install the upgraded version following the standard GoAutoDial upgrade procedure
  4. After upgrade, verify that go_site.php has been updated and the cpanel function no longer accepts unsanitized PATH_INFO input
  5. Test that the application functions normally with the new version

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

Fix this in Goadmin Ce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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