dbcve.org
Goadmin CeApplication · Goautodial

CVE-2015-2842

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
Unrestricted file upload vulnerability in go_audiostore.php in the audiostore (Voice Files) upload functionality in GoAutoDial GoAdmin CE 3.x before 3.3-1421902800 allows remote attackers to execute arbitrary code by uploading a file with an executable extension, then accessing it via a direct request to the file in sounds/.

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

Unrestricted file upload vulnerability in GoAutoDial GoAdmin CE 3.x allows remote attackers to upload files with executable extensions (e.g., .php) via the go_audiostore.php audiostore upload functionality. The uploaded files are stored in the sounds/ directory accessible via direct HTTP request, enabling arbitrary code execution.

MitigationRestrict uploads to safe audio file types only (e.g., .wav, .mp3, .flac) with server-side content-type validation; store uploads outside the web root or disable script execution in the sounds/ directory; upgrade to GoAdmin CE 3.3-1421902800 or later.

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
    Check if GoAdmin CE web interface is accessible. Look for /goadmin/go_auth.php or similar GoAdmin paths in the web root.
    Affected if GoAutoDial GoAdmin CE is installed on the server
  2. Determine the GoAdmin CE version
    Access the admin panel or check version files. Common paths include /goadmin/version.php or check the footer of the admin login page for version information.
    Affected if The installed version is 3.0 or 3.3 (exactly these versions)
  3. Locate the go_audiostore.php file
    Check if the file go_audiostore.php exists in the web-accessible directory, typically under /goadmin/ or the campaign sounds directory.
    Affected if The file go_audiostore.php exists and is accessible via HTTP
  4. Verify sounds directory is web-accessible
    Attempt to access the sounds/ or recordings/ directory via direct HTTP request (e.g., GET request to /sounds/). Check if directory listing is enabled or if files are directly accessible.
    Affected if The sounds/ directory is accessible via HTTP and allows direct file access
  5. Check for script execution in sounds directory
    Examine the web server configuration (Apache .htaccess, Nginx config) or attempt to access a test .php file placed in the sounds/ directory to see if it executes as PHP.
    Affected if PHP or other script execution is enabled in the sounds/ directory, allowing uploaded files to execute

The environment is affected if GoAdmin CE versions 3.0 or 3.3 are installed AND the go_audiostore.php upload feature is accessible AND the sounds/ directory allows script execution.

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

Restrict uploads to safe audio file types only (e.g., .wav, .mp3, .flac) with server-side content-type validation; store uploads outside the web root or disable script execution in the sounds/ directory; upgrade to GoAdmin CE 3.3-1421902800 or later.

Recommended fix Moderate confidence

GoAdmin CE 3.3-1421902800 or later

  1. 1. Backup the current GoAdmin CE installation and database before making any changes.
  2. 2. Download GoAdmin CE version 3.3-1421902800 or later from the official GoAutoDial repository (e.g., goautodial.org or official distribution channels).
  3. 3. Stop the GoAutoDial services (vicidial, asterisk, httpd) to ensure a stable upgrade process.
  4. 4. Install the upgraded GoAdmin CE package, following the standard upgrade procedure for GoAutoDial systems.
  5. 5. After installation, verify that go_audiostore.php has been updated and no longer allows unrestricted file uploads with executable extensions.
  6. 6. Restart all GoAutoDial services.
  7. 7. Test the audiostore upload functionality to confirm it no longer accepts executable files (e.g., .php, .exe, .sh).
  8. 8. Verify the sounds/ directory does not contain any malicious files uploaded before the patch.
Caveat Standard GoAutoDial upgrade risks apply - ensure backup and test in non-production environment first

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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