dbcve.org
DevexpressApplication

CVE-2023-35814

CRITICAL · 9.8 CVSS v3.1 Published 2025-04-28
Fix available
A fix is available. Upgrade to 21.2.12 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
DevExpress before 23.1.3 does not properly protect XtraReport serialized data in ASP.NET web forms.

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 confidence

DevExpress XtraReport before version 23.1.3 contains an insecure deserialization vulnerability in its ASP.NET web forms handling. The component fails to properly protect serialized data, allowing attackers to potentially execute arbitrary code by injecting malicious serialized objects through XtraReport data endpoints.

MitigationUpgrade DevExpress XtraReport to version 23.1.3 or later to obtain the patched libraries. If immediate upgrading is not feasible, review and restrict access to any endpoints handling XtraReport serialized data, and implement additional input validation or serialization guards.

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
DevexpressApplication
Affected:< 21.2.12= 22.1.8= 22.2.4= 22.2.5

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed DevExpress version
    Inspect the Bin folder for DevExpress assemblies (look for assemblies named DevExpress.XtraReports*.dll) or check packages.config, .csproj file, or the GAC for DevExpress version metadata. The version is typically embedded in the file version or assembly version attribute.
    Affected if The installed version is any of: less than 21.2.12, equal to 22.1.8, equal to 22.2.4, or equal to 22.2.5.
  2. Confirm XtraReport usage in the application
    Search the codebase for references to DevExpress XtraReports classes (such as XtraReport, XtraReportBase, or classes inheriting from them). Check .aspx markup files for ReportViewer controls or similar XtraReport-related controls.
    Affected if The application codebase contains XtraReport implementations or uses XtraReport controls in ASP.NET Web Forms pages.
  3. Identify endpoints processing serialized report data
    Review the application for .aspx pages or handlers that accept report data parameters (commonly parameters named reportName, reportXml, reportData, or containing serialized objects). Check HttpHandlers and HttpModules in web.config for report processing routes.
    Affected if The application exposes endpoints that accept and process XtraReport serialized data without authentication or additional validation.
  4. Check web.config serialization settings
    Examine the application's web.config file for serialization configuration related to XtraReports. Look for settings that enable binary serialization of report objects or allow ViewState/Request data to contain XtraReport serialized payloads.
    Affected if The configuration enables or permits deserialization of XtraReport data submitted via web requests.

You are affected if your installed DevExpress version matches the affected ranges AND your ASP.NET Web Forms application uses XtraReport to process serialized data submitted through web endpoints.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 21.2.12 or later
Fixed in 21.2.12
Interim mitigation

Upgrade DevExpress XtraReport to version 23.1.3 or later to obtain the patched libraries. If immediate upgrading is not feasible, review and restrict access to any endpoints handling XtraReport serialized data, and implement additional input validation or serialization guards.

Recommended fix High confidence

23.1.3 or later (any version after 23.1.3 contains the fix)

  1. 1. Identify the current DevExpress version installed in your ASP.NET web forms application
  2. 2. Download DevExpress version 23.1.3 or later from the official DevExpress website (https://www.devexpress.com/) or your licensed download area
  3. 3. Install the new DevExpress version following the official installation instructions
  4. 4. Rebuild and test your application to ensure XtraReport functionality works correctly with the updated libraries
  5. 5. Deploy the updated application to your production environment
Caveat Review DevExpress release notes for version 23.1.x for potential breaking changes in XtraReport or related components

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Devexpress Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-35814 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-35814 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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