dbcve.org
PlatformApplication · Orchid

CVE-2023-36825

CRITICAL · 9.8 CVSS v3.1 Published 2023-07-11
Fix available
A fix is available. Upgrade to 14.5.0 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
Orchid is a Laravel package that allows application development of back-office applications, admin/user panels, and dashboards. A vulnerability present starting in version 14.0.0-alpha4 and prior to version 14.5.0 is related to the deserialization of untrusted data from the `_state` query parameter, which can result in remote code execution. The issue has been addressed in version 14.5.0. Users are advised to upgrade their software to this version or any subsequent versions that include the patch. There are no known workarounds.

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 confidence

A deserialization vulnerability in the Orchid Laravel package allows remote code execution through the `_state` query parameter. The vulnerability affects versions 14.0.0-alpha4 through versions prior to 14.5.0, where untrusted data is deserialized without proper validation.

MitigationUpgrade Orchid to version 14.5.0 or later to remediate this vulnerability. There are no workarounds available.

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
PlatformApplication
Affected:>= 14.0.1, < 14.5.0= 14.0.0

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 Orchid package installation
    Run `composer show orchid/platform` to display the installed version of the Orchid Laravel package, or check the `composer.json` file for the orchid/platform version entry.
    Affected if The installed version is 14.0.0 or falls between 14.0.1 and 14.4.x inclusive.
  2. Locate the Orchid package version file
    If composer CLI is unavailable, inspect the `vendor/orchid/platform/composer.json` file directly to read the installed version number.
    Affected if The version listed is 14.0.0 or ranges from 14.0.1 up to but not including 14.5.0.
  3. Check for stateful query parameter usage
    Review application code for usage of the `_state` query parameter, which is used by Orchid's stateful filtering or screen state features. Search codebase for occurrences of `_state` in routes, controllers, or views.
    Affected if The application uses the `_state` parameter in any HTTP request handling, as this is the deserialization entry point.
  4. Verify deserialization of user input
    Examine Orchid's request handling logic, specifically looking for unserialize() calls that process the `_state` parameter value without validation. Check Orchid's screen state or filter state handling classes.
    Affected if The application deserializes the `_state` query parameter value without sanitization, which is the vulnerable behavior.

You are affected if the Orchid Laravel package is installed at version 14.0.0 or any version from 14.0.1 through 14.4.x and your application processes the `_state` query parameter.

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 14.5.0 or later
Fixed in 14.5.0
Interim mitigation

Upgrade Orchid to version 14.5.0 or later to remediate this vulnerability. There are no workarounds available.

Recommended fix High confidence

14.5.0

  1. Upgrade the Orchid Laravel package to version 14.5.0 or any subsequent version that includes the patch

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

Fix this in Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-36825 — 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-36825 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