CVE-2021-21263 [High] | Security Vulnerability in Laravel

Laravel is a web application framework. Versions of Laravel before 6.20.11, 7.30.2 and 8.22.1 contain a query binding exploitation. This same exploit applies to the illuminate/database package which is used by Laravel. If a request is crafted where a field that is normally a non-array value is an array, and that input is not validated or cast to its expected type before being passed to the query builder, an unexpected number of query bindings can be added to the query. In some situations, this will simply lead to no results being returned by the query builder; however, it is possible certain queries could be affected in a way that causes the query to return unexpected results.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-11-21	0.61%	1.14%	+0.53%
2	2025-11-18	1.14%	0.61%	-0.53%
3	2025-10-20	—	1.14%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-11-21

0.61%

1.14%

+0.53%

2025-11-18

1.14%

0.61%

-0.53%

2025-10-20

—

1.14%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.2	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	3.9	2.7	[email protected]
5.3	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	3.9	1.4	[email protected]
5.0	2.0	MEDIUM	`AV:N/AC:L/Au:N/C:N/I:P/A:N` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:N) No authentication is required. Confidentiality impact (C:N) No confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:N) No availability impact.	10.0	2.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.2

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

3.9

2.7

[email protected]

5.3

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

3.9

1.4

[email protected]

5.0

2.0

MEDIUM

AV:N/AC:L/Au:N/C:N/I:P/A:N Click to expand

Access vector (AV:N): Can be exploited remotely over network reachability.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:N): No confidentiality impact.
Integrity impact (I:P): Partial integrity impact.
Availability impact (A:N): No availability impact.

10.0

2.9

[email protected]

OS Trackers for CVE-2021-21263

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2021-21263 not yet assigned priority: Debian including 1 source packages (php-laravel-framework), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2021-21263
`ubuntu`	medium	CVE-2021-21263 medium priority: Ubuntu including 1 source packages (php-laravel-framework), 6 status rows across 6 suites (bionic, focal, groovy, trusty, upstream, xenial): DNE 5, released 1.	https://ubuntu.com/security/CVE-2021-21263

Affected software / configurations for CVE-2021-21263

Vendor	Product	Version	Raw CPE
laravel	laravel	>= 6.0.0, < 6.20.11	cpe:2.3:a:laravel:laravel::::::::
laravel	laravel	>= 7.0.0, < 7.30.2	cpe:2.3:a:laravel:laravel::::::::
laravel	laravel	>= 8.0.0, < 8.22.1	cpe:2.3:a:laravel:laravel::::::::

References for CVE-2021-21263

URL	Tags
https://blog.laravel.com/security-laravel-62011-7302-8221-released	Vendor Advisory
https://github.com/laravel/framework/pull/35865	Patch Third Party Advisory
https://github.com/laravel/framework/security/advisories/GHSA-3p32-j457-pg5x	Third Party Advisory
https://packagist.org/packages/illuminate/database	Product Third Party Advisory
https://packagist.org/packages/laravel/framework	Product Third Party Advisory

URL

CVE-2021-21263 | Query Binding Exploitation in Laravel

Exploit prediction scoring system (EPSS) score for CVE-2021-21263

Common vulnerability scoring system (CVSS) metrics for CVE-2021-21263

Weakness enumeration for CVE-2021-21263

GitHub Security Advisory for CVE-2021-21263

OS Trackers for CVE-2021-21263

Affected software / configurations for CVE-2021-21263

References for CVE-2021-21263