CVE-2022-46442
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 · unediteddedecms <=V5.7.102 is vulnerable to SQL Injection. In sys_ sql_ n query.php there are no restrictions on the sql query.
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 confidenceSQL injection vulnerability in Dedecms <=V5.7.102 in the sys_sql_n_query.php file allows unauthenticated attackers to inject malicious SQL commands due to the lack of input restrictions or parameterized queries on user-supplied SQL 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<= 5.7.102CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Dedecms installationLook for Dedecms files or directories on the web server. Typical installation paths include /dede/ (admin directory), /include/ folder, or check for files containing 'DedeCMS' text in headers.Affected if Dedecms is installed on the server.
-
Identify Dedecms versionCheck the version.php file in the /include/ directory or log into the Dedecms admin dashboard to view the version information typically displayed on the main admin page.Affected if The installed version is 5.7.102 or lower.
-
Locate the vulnerable fileSearch the web root for the file sys_sql_n_query.php. It is typically located in the /include/ directory or a similar include path within the Dedecms installation.Affected if The file sys_sql_n_query.php exists in the Dedecms installation.
-
Verify file accessibilityAttempt to access the sys_sql_n_query.php file directly via HTTP/HTTPS request without providing any authentication credentials. For example: GET /include/sys_sql_n_query.phpAffected if The file is accessible without authentication (returns HTTP 200 instead of redirecting to login or returning 403/404).
A user is affected if Dedecms is installed with version 5.7.102 or lower AND the sys_sql_n_query.php file exists and is accessible without authentication.
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 dataRestrict SQL query functionality by implementing parameterized queries, input validation, and proper sanitization of SQL inputs in sys_sql_n_query.php. If no official patch is available, disable or remove the affected functionality until proper remediation can be implemented.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46442 — 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-46442 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