dbcve.org
Gacjie ServerApplication · Gacjie Server Project

CVE-2024-2406

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-12
Fix available
A fix is available. Upgrade to after 1.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
A vulnerability, which was classified as critical, was found in Gacjie Server up to 1.0. This affects the function index of the file /app/admin/controller/Upload.php. The manipulation of the argument file leads to unrestricted upload. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-256503.

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 the index function of /app/admin/controller/Upload.php in Gacjie Server up to v1.0 allows remote attackers to upload malicious files (e.g., web shells) directly to the web server without proper validation of file type or content. The lack of input sanitization on the 'file' argument enables unauthenticated remote code execution.

MitigationImplement strict allowlist-based file type validation using both magic byte verification and extension checking; store uploads outside the web root; disable script execution in upload directories; apply vendor patch when available.

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
Gacjie ServerApplication
Affected:<= 1.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.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. Identify if Gacjie Server is deployed
    Locate the application installation directory and confirm it is the Gacjie Server project. Check for the presence of typical Gacjie Server file structure including the /app/admin/controller/ directory.
    Affected if The system is running Gacjie Server and the file /app/admin/controller/Upload.php exists in the installation.
  2. Determine the installed Gacjie Server version
    Locate the version file or metadata within the Gacjie Server installation (such as a version.php, composer.json, or changelog file) and read the version number.
    Affected if The installed version is 1.0 or any version number lower than 1.0, as the vulnerability affects versions up to and including 1.0.
  3. Verify the vulnerable Upload controller exists
    Inspect the file system for /app/admin/controller/Upload.php and confirm the index function is present within it.
    Affected if The file /app/admin/controller/Upload.php exists and contains an index function that handles file uploads without proper validation.
  4. Search for unexpected file types in web-accessible directories
    Scan directories that are served by the web server (such as /public/, /uploads/, /static/, or the web root) for file extensions that indicate executable content, including .php, .phtml, .php5, .php7, .asp, .aspx, .jsp, or .exe.
    Affected if Unexpected script files (.php, .phtml, etc.) are found in web-accessible directories, especially if they were not deliberately placed there by administrators.
  5. Review web server access logs for upload endpoint activity
    Examine web server access logs (typically found in /var/log/nginx/, /var/log/apache2/, or similar locations) for POST requests to /app/admin/controller/Upload.php or /index.php/admin/upload/index.
    Affected if Log entries show POST requests to the upload endpoint that resulted in successful HTTP 200 responses, indicating files may have been uploaded.

A system is affected if it runs Gacjie Server version 1.0 or lower, contains the vulnerable Upload.php controller, and either shows suspicious script files in web directories or exhibits log evidence of upload attempts to the unprotected endpoint.

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 1.0
Interim mitigation

Implement strict allowlist-based file type validation using both magic byte verification and extension checking; store uploads outside the web root; disable script execution in upload directories; apply vendor patch when available.

Fix this in Gacjie Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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