CVE-2026-0843: SQL Injection in jiujiujia jjjfood
CVE-2026-0843 is a medium severity SQL injection vulnerability affecting the jiujiujia jjjfood and jjjshop_food products up to version 20260103. The flaw exists in the /index. php/api/product. category/index endpoint, where manipulation of the latitude parameter allows remote attackers to inject SQL commands without authentication or user interaction. The vulnerability has been publicly disclosed, but no patch or vendor response is available. Exploitation could lead to unauthorized data access or modification, impacting confidentiality, integrity, and availability of backend databases. The CVSS 4. 0 score is 5. 3, reflecting network attack vector, low complexity, no privileges or user interaction required, but limited scope and impact. European organizations using these products or their variants should prioritize mitigation to prevent data breaches or service disruption.
AI Analysis
Technical Summary
CVE-2026-0843 is a SQL injection vulnerability identified in the jiujiujia jjjfood and jjjshop_food software products, specifically affecting versions up to 20260103. The vulnerability resides in the handling of the 'latitude' parameter within the /index.php/api/product.category/index API endpoint. An attacker can remotely manipulate this parameter to inject malicious SQL queries into the backend database without requiring authentication or user interaction. This injection flaw allows attackers to potentially read, modify, or delete sensitive data stored in the database, compromising confidentiality, integrity, and availability. The vulnerability has been publicly disclosed, but the vendor has not responded or provided patches, increasing the risk of exploitation. The CVSS 4.0 base score is 5.3, indicating medium severity, with an attack vector over the network, low attack complexity, no privileges required, and no user interaction needed. The impact is limited to the vulnerable component, but the potential for data leakage or corruption remains significant. The product is distributed under multiple names, complicating detection and mitigation efforts. No known exploits are currently reported in the wild, but public disclosure increases the likelihood of future exploitation attempts.
Potential Impact
For European organizations using jjjfood or jjjshop_food products, this vulnerability poses a risk of unauthorized access to sensitive business or customer data through SQL injection attacks. Exploitation could lead to data breaches, data tampering, or denial of service if attackers manipulate database queries maliciously. This can result in financial losses, reputational damage, and regulatory penalties under GDPR due to compromised personal data. Supply chain dependencies on these products in retail, food delivery, or inventory management systems could amplify the impact by affecting multiple organizations. The lack of vendor response and patches increases the window of exposure, making proactive mitigation critical. Organizations relying on these products for critical operations may face service disruptions or data integrity issues, impacting business continuity.
Mitigation Recommendations
Organizations should immediately audit their environments to identify any deployments of jjjfood, jjjshop_food, or their variants. Since no official patch is available, implement the following mitigations: 1) Apply strict input validation and sanitization on the 'latitude' parameter at the web application firewall (WAF) or API gateway level to block malicious SQL payloads. 2) Employ parameterized queries or prepared statements in any custom code interfacing with the vulnerable API if source code access is possible. 3) Monitor logs for unusual or suspicious requests targeting the /index.php/api/product.category/index endpoint, especially those manipulating the latitude parameter. 4) Restrict network access to the vulnerable API endpoints to trusted internal networks where feasible. 5) Consider deploying runtime application self-protection (RASP) solutions to detect and block injection attempts dynamically. 6) Engage with the vendor or community to track any forthcoming patches or updates. 7) Prepare incident response plans to quickly address potential exploitation attempts. 8) Conduct security awareness training for developers and administrators on secure coding and input validation best practices.
Affected Countries
Germany, France, Italy, Spain, Netherlands, Poland, United Kingdom
CVE-2026-0843: SQL Injection in jiujiujia jjjfood
Description
CVE-2026-0843 is a medium severity SQL injection vulnerability affecting the jiujiujia jjjfood and jjjshop_food products up to version 20260103. The flaw exists in the /index. php/api/product. category/index endpoint, where manipulation of the latitude parameter allows remote attackers to inject SQL commands without authentication or user interaction. The vulnerability has been publicly disclosed, but no patch or vendor response is available. Exploitation could lead to unauthorized data access or modification, impacting confidentiality, integrity, and availability of backend databases. The CVSS 4. 0 score is 5. 3, reflecting network attack vector, low complexity, no privileges or user interaction required, but limited scope and impact. European organizations using these products or their variants should prioritize mitigation to prevent data breaches or service disruption.
AI-Powered Analysis
Technical Analysis
CVE-2026-0843 is a SQL injection vulnerability identified in the jiujiujia jjjfood and jjjshop_food software products, specifically affecting versions up to 20260103. The vulnerability resides in the handling of the 'latitude' parameter within the /index.php/api/product.category/index API endpoint. An attacker can remotely manipulate this parameter to inject malicious SQL queries into the backend database without requiring authentication or user interaction. This injection flaw allows attackers to potentially read, modify, or delete sensitive data stored in the database, compromising confidentiality, integrity, and availability. The vulnerability has been publicly disclosed, but the vendor has not responded or provided patches, increasing the risk of exploitation. The CVSS 4.0 base score is 5.3, indicating medium severity, with an attack vector over the network, low attack complexity, no privileges required, and no user interaction needed. The impact is limited to the vulnerable component, but the potential for data leakage or corruption remains significant. The product is distributed under multiple names, complicating detection and mitigation efforts. No known exploits are currently reported in the wild, but public disclosure increases the likelihood of future exploitation attempts.
Potential Impact
For European organizations using jjjfood or jjjshop_food products, this vulnerability poses a risk of unauthorized access to sensitive business or customer data through SQL injection attacks. Exploitation could lead to data breaches, data tampering, or denial of service if attackers manipulate database queries maliciously. This can result in financial losses, reputational damage, and regulatory penalties under GDPR due to compromised personal data. Supply chain dependencies on these products in retail, food delivery, or inventory management systems could amplify the impact by affecting multiple organizations. The lack of vendor response and patches increases the window of exposure, making proactive mitigation critical. Organizations relying on these products for critical operations may face service disruptions or data integrity issues, impacting business continuity.
Mitigation Recommendations
Organizations should immediately audit their environments to identify any deployments of jjjfood, jjjshop_food, or their variants. Since no official patch is available, implement the following mitigations: 1) Apply strict input validation and sanitization on the 'latitude' parameter at the web application firewall (WAF) or API gateway level to block malicious SQL payloads. 2) Employ parameterized queries or prepared statements in any custom code interfacing with the vulnerable API if source code access is possible. 3) Monitor logs for unusual or suspicious requests targeting the /index.php/api/product.category/index endpoint, especially those manipulating the latitude parameter. 4) Restrict network access to the vulnerable API endpoints to trusted internal networks where feasible. 5) Consider deploying runtime application self-protection (RASP) solutions to detect and block injection attempts dynamically. 6) Engage with the vendor or community to track any forthcoming patches or updates. 7) Prepare incident response plans to quickly address potential exploitation attempts. 8) Conduct security awareness training for developers and administrators on secure coding and input validation best practices.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulDB
- Date Reserved
- 2026-01-10T10:02:26.170Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6963689dda2266e8386cdffb
Added to database: 1/11/2026, 9:08:45 AM
Last enriched: 1/19/2026, 7:40:47 AM
Last updated: 2/7/2026, 11:09:18 AM
Views: 68
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-2083: SQL Injection in code-projects Social Networking Site
MediumCVE-2026-2082: OS Command Injection in D-Link DIR-823X
MediumCVE-2026-2080: Command Injection in UTT HiPER 810
HighCVE-2026-2079: Improper Authorization in yeqifu warehouse
MediumCVE-2026-1675: CWE-1188 Initialization of a Resource with an Insecure Default in brstefanovic Advanced Country Blocker
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.