CVE-2024-11017
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 · uneditedWebopac from Grand Vice info does not properly validate uploaded file types, allowing remote attackers with regular privileges to upload and execute webshells, which could lead to arbitrary code execution on the server.
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 confidenceWebopac from Grand Vice info contains a file upload vulnerability where the application fails to properly validate the type of uploaded files. Attackers with regular user privileges can upload malicious files (webshells) through the application's upload functionality. Because the uploaded files are not properly validated or restricted, they can be executed on the server, leading to arbitrary code execution.
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>= 6, < 6.5.1>= 7, < 7.2.3CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Webopac versionLocate the version information in the application's admin panel, about page, or configuration files (typically found in installation directory or web application metadata)Affected if The version is 6.x (before 6.5.1) or 7.x (before 7.2.3)
-
Confirm file upload functionality existsAccess the user-facing portion of the application and locate any file upload feature (commonly in user profile, document library, or resource upload sections)Affected if The application has a file upload feature accessible to regular authenticated users
-
Verify upload validation is absent or weakInspect the upload configuration or attempt a test upload with a non-standard file extension (such as .php, .exe, or .jsp) to see if the application accepts it without rejecting based on file typeAffected if The application accepts files without proper extension allowlisting, MIME type verification, or magic byte validation
-
Check uploaded file storage locationExamine the web server configuration or uploaded files directory to determine if uploaded files are stored within the webroot and retain their original extensionsAffected if Uploaded files are stored inside the webroot and can be accessed directly via URL with their original filename and extension
If your Webopac version falls within 6.0 to 6.5.0 or 7.0 to 7.2.2 AND the file upload feature is accessible to regular users without strict validation, your environment is likely affected by this CVE.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.5.17.2.3
Implement strict file type validation using a combination of extension allowlists, MIME type verification, and magic byte inspection. Store uploaded files outside the webroot with no execute permissions, or rename files and serve them through a handler that forces download instead of execution.
Webopac 6.5.1 or later for v6.x branch; Webopac 7.2.3 or later for v7.x branch
- Identify the currently installed Webopac version by checking the application or system documentation
- Determine which version branch (6.x or 7.x) is currently in use
- For Webopac 6.x users: Upgrade to version 6.5.1 or later
- For Webopac 7.x users: Upgrade to version 7.2.3 or later
- After upgrading, verify that file upload functionality properly validates file types and rejects executable files such as .php, .asp, .jsp, .exe, or .sh
- Confirm the upgrade was successful by checking the new version number in the system
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2024-11017 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-11017 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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