dbcve.org
WuhuApplication · Gargaj

CVE-2024-6948

CRITICAL · 9.8 CVSS v3.1 Published 2024-07-21
Fix available
A fix is available. Upgrade to after 2024-02-10 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 classified as critical has been found in Gargaj wuhu up to 3faad49bfcc3895e9ff76a591d05c8941273d120. Affected is an unknown function of the file /slideeditor.php of the component Slide Editor. The manipulation of the argument newSlideFile leads to unrestricted upload. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. VDB-272070 is the identifier assigned to this vulnerability.

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

The Gargaj wuhu application contains an unrestricted file upload vulnerability in the Slide Editor component (slideeditor.php). The 'newSlideFile' argument is not properly validated, allowing remote attackers to upload arbitrary files including malicious executables to the server.

MitigationImplement strict server-side file validation including allowlist of permitted file types, file content/magic byte verification, filename sanitization, and store uploads outside the webroot or with non-executable permissions.

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
WuhuApplication
Affected:<= 2024-02-10

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 Gargaj Wuhu installation and version
    Locate the Gargaj Wuhu application directory and check the version information (typically in application metadata, version file, or about screen). Compare against the affected version: <= 2024-02-10
    Affected if The installed version of Gargaj Wuhu is 2024-02-10 or earlier
  2. Verify slideeditor.php component exists
    Search for the file slideeditor.php within the application web directory or source code
    Affected if The slideeditor.php file exists in the application installation
  3. Confirm web server exposure
    Check if the application directory containing slideeditor.php is accessible via the web server (HTTP/HTTPS). This typically involves reviewing web server configuration, virtual host settings, or document root mappings
    Affected if The slideeditor.php component is reachable over the network through the web server
  4. Check if file upload feature is accessible
    Examine the slideeditor.php file to determine if the newSlideFile parameter handling is present and exposed. Review application routing or access control configuration to confirm the upload endpoint is not blocked or authentication-protected
    Affected if The slideeditor.php upload functionality (newSlideFile parameter) is accessible without additional security controls
  5. Inspect uploaded files storage location
    Review the application configuration and file system to identify where slide files are stored. Check if uploads are placed within the webroot with executable permissions
    Affected if Uploaded files are stored inside the web-accessible directory with executable permissions

The environment is affected if Gargaj Wuhu version 2024-02-10 or earlier is installed, the slideeditor.php component is web-accessible, and the newSlideFile upload functionality is exposed without proper validation controls.

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 2024-02-10
Interim mitigation

Implement strict server-side file validation including allowlist of permitted file types, file content/magic byte verification, filename sanitization, and store uploads outside the webroot or with non-executable permissions.

Fix this in Wuhu Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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