Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-0843: SQL Injection in jiujiujia jjjfood

0
Medium
VulnerabilityCVE-2026-0843cvecve-2026-0843
Published: Sun Jan 11 2026 (01/11/2026, 09:02:05 UTC)
Source: CVE Database V5
Vendor/Project: jiujiujia
Product: jjjfood

Description

A vulnerability has been found in jiujiujia/victor123/wxw850227 jjjfood and jjjshop_food up to 20260103. This vulnerability affects unknown code of the file /index.php/api/product.category/index. Such manipulation of the argument latitude leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. This product is distributed under multiple different names. The vendor was contacted early about this disclosure but did not respond in any way.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/23/2026, 22:46:02 UTC

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 /index.php/api/product.category/index endpoint, where the latitude parameter is improperly sanitized, allowing an attacker to inject malicious SQL code. This injection flaw can be exploited remotely without requiring authentication or user interaction, making it highly accessible to attackers. The vulnerability impacts the confidentiality, integrity, and availability of the backend database by enabling unauthorized data access, modification, or deletion. The products affected are distributed under multiple aliases, complicating detection and mitigation efforts. Despite early notification, the vendor has not responded or issued a patch, and the exploit has been publicly disclosed, increasing the risk of exploitation. The CVSS v4.0 score is 5.3 (medium severity), reflecting the ease of exploitation and potential impact. The vulnerability does not require special privileges or user interaction, but the impact on data security is significant. Organizations using these products should conduct immediate security assessments and implement compensating controls to mitigate risk.

Potential Impact

The SQL injection vulnerability allows attackers to execute arbitrary SQL commands on the backend database, potentially leading to unauthorized data disclosure, data manipulation, or deletion. This can compromise sensitive business and customer information, disrupt normal operations, and damage organizational reputation. Since the flaw can be exploited remotely without authentication, attackers can launch automated attacks at scale, increasing the likelihood of widespread compromise. The lack of vendor response and patch availability prolongs exposure, raising the risk of successful exploitation. Organizations relying on jjjfood or jjjshop_food products may face regulatory compliance issues if sensitive data is breached. The distribution of the affected product under multiple names increases the chance that some deployments remain unpatched or unrecognized, further expanding the attack surface. Overall, the vulnerability poses a moderate risk but with potential for significant operational and data security impacts if exploited.

Mitigation Recommendations

1. Immediately audit all deployments of jjjfood and jjjshop_food products, including those under alternative names, to identify affected versions. 2. Implement Web Application Firewall (WAF) rules specifically designed to detect and block SQL injection attempts targeting the latitude parameter in the /index.php/api/product.category/index endpoint. 3. Employ input validation and parameterized queries or prepared statements in the application code to prevent SQL injection; if source code access is available, prioritize fixing the root cause. 4. Monitor logs for suspicious activity related to the vulnerable endpoint, including unusual query patterns or error messages indicative of injection attempts. 5. Restrict database user permissions to the minimum necessary to limit the impact of potential SQL injection exploitation. 6. If vendor patches become available, apply them promptly. 7. Consider network segmentation and access controls to limit exposure of the vulnerable application to untrusted networks. 8. Educate security teams about this vulnerability and ensure incident response plans include detection and mitigation steps for SQL injection attacks.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

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: 2/23/2026, 10:46:02 PM

Last updated: 3/24/2026, 2:51:06 PM

Views: 101

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses