CVE-2022-43196
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 · unediteddedecmdv6 v6.1.9 is vulnerable to Arbitrary file deletion via file_manage_control.php.
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 · moderate confidencededecmdv6 v6.1.9 contains an arbitrary file deletion vulnerability in file_manage_control.php that allows attackers to delete arbitrary files on the server, likely due to insufficient input validation or authorization checks on file operation parameters.
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.1.9CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 if Dedecmsv6 is installedLook for Dedecms installation directories on the web server, such as /dedecms/, /cms/, or the root web directory. Check for characteristic files like /include/common.inc.php or /install/index.phpAffected if Dedecmsv6 installation is found on the server
-
Verify the installed versionAccess the admin dashboard or check version files. In Dedecms, version information is often displayed in the footer of the admin panel or stored in version-specific configuration filesAffected if The installed version is exactly 6.1.9
-
Confirm file_manage_control.php existsLocate the file file_manage_control.php within the Dedecms installation directory, typically under /include/ or /dede/ (admin) directoryAffected if The file exists in the installation
-
Check if the file is accessible without authenticationAttempt to access file_manage_control.php directly via HTTP request without logging in, or examine the file source code for authentication checks around file deletion functionsAffected if The file responds without requiring valid admin credentials or authentication tokens
-
Inspect the file deletion logicExamine the source code of file_manage_control.php for parameters used in file deletion operations (such as filename, filepath, or activefile parameters). Check if these parameters accept path traversal sequences like ../Affected if The code accepts user-controlled path parameters without sanitization or validation
The environment is affected if Dedecmsv6 version 6.1.9 is installed and the file_manage_control.php file is accessible, as this version contains the arbitrary file deletion vulnerability in that component.
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.
From vendor dataApply authentication and proper input validation with path traversal prevention to all file operation functions in file_manage_control.php; restrict file deletion permissions to authorized users only.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43196 — 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-2022-43196 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