dbcve.org
Goadmin CeApplication · Goautodial

CVE-2015-2844

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
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-1420434000 allows remote attackers to execute arbitrary commands via the $action 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 the cpanel function of go_site.php in GoAutoDial GoAdmin CE allows remote unauthenticated attackers to execute arbitrary OS commands via the $action PATH_INFO parameter.

MitigationUpgrade to GoAutoDial GoAdmin CE version 3.3-1420434000 or later, or implement input sanitization/validation on the $action parameter in go_site.php to prevent shell command injection.

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 version
    Check the installed version of GoAutoDial GoAdmin CE by reviewing the application release files, package manager output, or the admin interface version display
    Affected if The installed version is 3.0 or 3.3 (exact match to the affected versions)
  2. Locate go_site.php file
    Find the go_site.php file in the GoAutoDial web directory, typically in /var/www/html or the document root where GoAutoDial is installed
    Affected if The file exists and is accessible via web server
  3. Verify cpanel function is exposed
    Examine go_site.php to confirm the cpanel function exists and is accessible without authentication (the CVE states remote unauthenticated attackers can exploit it)
    Affected if The cpanel function is present and accessible without authentication
  4. Inspect $action parameter handling
    Review the code in go_site.php that handles the $action PATH_INFO parameter to see if user input is passed to shell execution functions without sanitization
    Affected if The $action parameter is used in shell execution (such as exec, shell_exec, system, or passthru) without proper input validation

If GoAutoDial GoAdmin CE version 3.0 or 3.3 is installed AND go_site.php with an unauthenticated cpanel function exists with unsafe $action parameter handling, the environment is affected by CVE-2015-2844.

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 GoAutoDial GoAdmin CE version 3.3-1420434000 or later, or implement input sanitization/validation on the $action parameter in go_site.php to prevent shell command injection.

Recommended fix High confidence

GoAdmin CE 3.3-1420434000 or later

  1. 1. Verify the current GoAdmin CE version installed by checking the admin interface or system documentation
  2. 2. Download GoAdmin CE version 3.3-1420434000 or later from the official GoAutoDial repository (goautodial.org)
  3. 3. Backup the current GoAdmin CE installation and database before upgrading
  4. 4. Follow the official upgrade instructions provided by GoAutoDial for upgrading from version 3.0 or earlier 3.x versions to 3.3-1420434000 or later
  5. 5. After upgrade, verify the go_site.php file has been updated and no longer contains the vulnerable cpanel function accessible via PATH_INFO
  6. 6. Test that the application functions normally after the upgrade
Caveat Review GoAutoDial release notes for any configuration or feature changes between 3.0/3.3 and the target 3.3-1420434000 release

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

Fix this in Goadmin Ce Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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