PatchSiren cyber security CVE debrief
CVE-2021-47811 Grocery Crud CVE debrief
CVE-2021-47811 is a SQL injection vulnerability in Grocery Crud 1.6.4 that allows remote attackers to manipulate database queries through the order_by parameter in POST requests to the ajax_list endpoint. This vulnerability can potentially allow attackers to extract or modify database information. Defenders and administrators of Grocery Crud 1.6.4 systems should assess exposure and potential impact, and implement compensating controls to restrict database access. The CVE record and NVD entry provide details on the vulnerability.
- Vendor
- Grocery Crud
- Product
- Grocery Crud
- CVSS
- HIGH 8.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-01-15
- Original CVE updated
- 2026-11-07
- Advisory published
- 2026-01-15
- Advisory updated
- 2026-11-07
Who should care
Defenders and administrators of Grocery Crud 1.6.4 systems should assess exposure and potential impact. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify exposure, assess potential impact, and implement compensating controls to restrict database access.
Why it matters
CVE-2021-47811 is a SQL injection vulnerability in Grocery Crud 1.6.4 that allows remote attackers to manipulate database queries.
- Verify exposure by checking system versions and configurations.
- Assess potential impact on database integrity and confidentiality.
- Implement compensating controls to restrict database access.
- Monitor for suspicious database activity.
Technical summary
Grocery Crud 1.6.4 contains a SQL injection vulnerability in the order_by parameter of the ajax_list endpoint in POST requests. This allows remote attackers to manipulate database queries, potentially leading to extraction or modification of database information. The vulnerability is confirmed by the CVE record and NVD entry, and defenders should prioritize verifying exposure and assessing potential impact. Compensating controls should be implemented to restrict database access, and monitoring for suspicious database activity is recommended.
Defensive priority
Defenders should prioritize verifying exposure and assessing potential impact.
Recommended defensive actions
- Verify exposure by checking system versions and configurations.
- Assess potential impact on database integrity and confidentiality.
- Implement compensating controls to restrict database access.
- Monitor for suspicious database activity.
- Review vendor patch guidance for Grocery Crud 1.6.4.
- Conduct an exposure review of current deployments.
- Perform asset inventory to identify potentially affected systems.
Evidence notes
The CVE record and NVD entry provide details on the SQL injection vulnerability in Grocery Crud 1.6.4. The vulnerability is in the order_by parameter of the ajax_list endpoint in POST requests. The details are based on the official CVE Program record and the NIST NVD detail page. There are also third-party advisories and product information available.
Sources and references
Verified primary and authoritative sources
-
CVE-2021-47811 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2021-47811
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2021-47811 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2021-47811
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://www.exploit-db.com/exploits/49985
[email protected] - Exploit
-
Source reference
Unverified legacy reference
URL: https://www.grocerycrud.com/
[email protected] - Product
-
Source reference
Unverified legacy reference
URL: https://www.grocerycrud.com/downloads
[email protected] - Product
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/grocery-crud-orderby-sql-injection
[email protected] - Third Party Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.