CVE-2025-61810
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 · uneditedColdFusion versions 2025.4, 2023.16, 2021.22 and earlier are affected by a Deserialization of Untrusted Data vulnerability that could result in arbitrary code execution in the context of the current user. A high privileged attacker could exploit this vulnerability by providing maliciously crafted serialized data to the application. Exploitation of this issue requires user interaction and scope is changed.
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 confidenceColdFusion versions 2025.4, 2023.16, 2021.22 and earlier contain a deserialization vulnerability where a high-privileged attacker can supply maliciously crafted serialized data to achieve arbitrary code execution. Exploitation requires user interaction and involves a changed scope, indicating the attack can impact resources beyond the vulnerable component.
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= 2021= 2023= 2025CVSS 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
- High
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/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 installed ColdFusion versionAccess the ColdFusion Administrator console (typically at /cfadmin or /CFIDE/administrator) and check the version displayed on the login or system overview page. Alternatively, check the version file in the ColdFusion installation directory or run: cfadmin -v from the command line.Affected if The installed version is 2021 (any update), 2023 (any update), 2025 (any update), or specifically 2021.22 and earlier, 2023.16 and earlier, 2025.4 and earlier.
-
Determine if deserialization features are enabledReview the ColdFusion Administrator settings under Server Settings > Java Applets or look for deserialization-related configurations in the neo-*.xml files within the /lib directory. Check if the CFIDE/administrator/serialization/ endpoint or similar serialization interfaces are accessible.Affected if Deserialization endpoints or features are exposed and accessible without additional restrictions.
-
Review deserialization-related configuration filesInspect configuration files in the ColdFusion installation directory (typically under /cfusion/lib or /ColdFusion2021/lib) for custom deserialization settings. Look for files like appcfc.java or any custom Java object instantiations that handle serialized data.Affected if Custom deserialization handlers or unsafe object instantiation configurations are present.
-
Audit high-privileged user accessReview the ColdFusion Administrator user accounts and their permission levels. Check the users.xml or underlying user store for accounts with Administrator or elevated privileges that could supply serialized data.Affected if Multiple high-privileged accounts exist or guest/anonymous access is granted elevated permissions.
-
Check for suspicious deserialization activity in logsExamine ColdFusion logs in the /logs directory (especially application.log, server.log, and exception.log) for entries containing patterns like 'ObjectInputStream', 'deserialize', 'ClassNotFoundException', or unexpected Java class loading.Affected if Logs contain deserialization attempts, especially from unexpected sources or with unusual payload patterns.
A user is affected if their ColdFusion installation version falls within 2021 (any), 2023 (any), or 2025 (any) up to the patched releases, AND deserialization endpoints are accessible or high-privileged accounts exist that could trigger the vulnerability.
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 · scopedUpgrade ColdFusion to the latest patched version beyond the affected releases (2025.4, 2023.16, 2021.22). In the interim, restrict deserialization capabilities, limit high-privileged access, and monitor for suspicious deserialization activity.
Upgrade to ColdFusion 2021 Update 23, ColdFusion 2023 Update 17, or ColdFusion 2025 Update 5 (or later respective versions)
- 1. Identify the current ColdFusion version by checking the ColdFusion Administrator or the version information in the installation
- 2. For ColdFusion 2021: Upgrade to version 2021.23 or later
- 3. For ColdFusion 2023: Upgrade to version 2023.17 or later
- 4. For ColdFusion 2025: Upgrade to version 2025.5 or later
- 5. Download the appropriate update from the Adobe ColdFusion downloads page (helpx.adobe.com)
- 6. Apply the update following Adobe's standard update installation procedures
- 7. After upgrade, verify the ColdFusion services restart successfully
- 8. Test critical applications to ensure functionality is maintained
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61810 — 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-2025-61810 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