LiveActive security incident?Get immediate response
CVE Record

CVE-2021-4262: laravel-jqgrid EloquentRepositoryAbstract.php getRows sql injection

A vulnerability classified as critical was found in laravel-jqgrid. Affected by this vulnerability is the function getRows of the file src/Mgallegos/LaravelJqgrid/Repositories/EloquentRepositoryAbstract.php. The manipulation leads to sql injection. The name of the patch is fbc2d94f43d0dc772767a5bdb2681133036f935e. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-216271.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-4262 is a SQL injection flaw in laravel-jqgrid's getRows function. If a vulnerable application uses this package, manipulated input could affect database queries, creating confidentiality, integrity, and availability risk. The sources name a patch commit but do not identify affected versions.

Executive priority

Treat as a scoped remediation item for applications that use laravel-jqgrid. It is not supported as actively exploited in the provided sources, but SQL injection can affect sensitive data, so confirm exposure and patch during the next security maintenance cycle.

Technical view

The issue affects getRows in src/Mgallegos/LaravelJqgrid/Repositories/EloquentRepositoryAbstract.php. The CVSS 3.1 vector is 5.5 medium: AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L. The record maps it to CWE-707 and references patch commit fbc2d94f43d0dc772767a5bdb2681133036f935e.

Likely exposure

Exposure is most likely in Laravel applications using laravel-jqgrid with the vulnerable repository code. The source bundle does not provide affected version ranges, package release names, or CPEs, so teams must confirm by dependency inventory and code comparison.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector requires low privileges and adjacent-network access, with no user interaction. Public references describe the vulnerability and patch, not confirmed exploitation activity.

Researcher notes

Key gaps are affected versions, precise input vector, and exploit telemetry. Validation should focus on whether the deployed getRows implementation predates the patch and whether public routes expose package-driven query construction to authenticated or adjacent users.

Mitigation direction

  • Apply the referenced patch commit or update to a release that includes it.
  • Check upstream vendor guidance because affected versions are not listed.
  • Restrict access to affected grid endpoints until patch status is confirmed.
  • Review application authorization around laravel-jqgrid-backed data views.

Validation and detection

  • Inventory applications using laravel-jqgrid and identify deployed code revisions.
  • Compare EloquentRepositoryAbstract.php against the referenced patched commit.
  • Add regression tests for safe handling of grid query parameters.
  • Review database logs for unusual query errors from grid endpoints.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-707: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-4262 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L2.13.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2021-4262Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
unspecifiedlaravel-jqgridn/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-707 · source CWE mapping

Improper Neutralization

Improper Neutralization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.