CVE-2022-2870Public exploitNetwork attack vector

Remote command execution via developer-added unserialize call

Published Aug 17, 2022 · Updated Apr 15, 2025

Deserialization in a custom Laravel Framework 5.1 controller allows remote attackers to execute commands through a crafted serialized object. The published proof of concept adds UsersController::store, which passes the cmd request parameter directly to PHP unserialize() before supplying a gadget-chain payload. Reachability requires an application developer to add the unauthenticated route and unsafe sink shown in the proof of concept, so the cited material does not establish an intrinsic framework flaw.

CVSS severity9.8
Critical
EPSS probability0.81%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Deserialization in a custom Laravel Framework 5.1 controller allows remote attackers to execute commands through a crafted serialized object. The published proof of concept adds UsersController::store, which passes the cmd request parameter directly to PHP unserialize() before supplying a gadget-chain payload. Reachability requires an application developer to add the unauthenticated route and unsafe sink shown in the proof of concept, so the cited material does not establish an intrinsic framework flaw.

The record

CVE
CVE-2022-2870
Published
Aug 17, 2022
Updated
Apr 15, 2025
Vendor
Laravel
Product
Laravel Framework
Classifications
CWE-502, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 17, 2022CVE publishedPublication date reported by the CVE source.
  2. Apr 15, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=5.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Laravel · Laravel Frameworkversion=5.1

Published CVSS scores

9.8NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.1VulDBCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-502Deserialization of Untrusted Data
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo