CVE-2022-24789
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 · uneditedC1 CMS is an open-source, .NET based Content Management System (CMS). Versions prior to 6.12 allow an authenticated user to exploit Server Side Request Forgery (SSRF) by causing the server to make arbitrary GET requests to other servers in the local network or on localhost. The attacker may also truncate arbitrary files to zero size (effectively delete them) leading to denial of service (DoS) or altering application logic. The authenticated user may unknowingly perform the actions by visiting a specially crafted site. Patched in C1 CMS v6.12, no known workarounds exist.
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 confidenceC1 CMS versions prior to 6.12 contain two vulnerabilities exploitable by authenticated users: Server-Side Request Forgery (SSRF) allowing the server to make arbitrary GET requests to internal/local resources, and arbitrary file truncation that can zero-out files causing denial of service or altering application logic. The attacker can trigger these by tricking authenticated users into visiting specially crafted sites.
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.12CVSS 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
- Low
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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.
-
Determine installed C1 CMS versionAccess the C1 CMS administration console or check the assembly/package version file in the installation directoryAffected if Version is lower than 6.12
-
Confirm user authentication is configuredVerify that C1 CMS has user accounts and login functionality enabled in the systemAffected if Authentication is active and users can log in to the CMS
-
Check for external request handling featuresReview the CMS installation for modules that handle outgoing HTTP requests from the server sideAffected if The CMS has functionality that processes external URLs or makes server-side GET requests
-
Inspect file operation capabilitiesExamine the CMS for features that allow authenticated users to modify or truncate files on the serverAffected if File modification features are accessible to authenticated users
The environment is affected if running any C1 CMS version prior to 6.12 with user authentication enabled, as the SSRF and file truncation vulnerabilities require an authenticated user session to be exploited.
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.12
Upgrade to C1 CMS v6.12 or later. No workarounds exist; the vendor recommends immediate patching.
C1 CMS v6.12 or later
- 1. Back up the existing C1 CMS database and application files before upgrading.
- 2. Download C1 CMS version 6.12 or later from the official C1 CMS repository or distribution channel.
- 3. Upgrade the C1 CMS installation to version 6.12 following the standard upgrade procedure.
- 4. Verify the upgrade completed successfully by checking the CMS version in the admin interface.
- 5. Test that the SSRF vulnerability is no longer exploitable by attempting to trigger requests to localhost or internal network resources.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24789 — 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-24789 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