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-5150: SQL Injection in code-projects Accounting System

0
Medium
VulnerabilityCVE-2026-5150cvecve-2026-5150
Published: Mon Mar 30 2026 (03/30/2026, 19:45:13 UTC)
Source: CVE Database V5
Vendor/Project: code-projects
Product: Accounting System

Description

A security vulnerability has been detected in code-projects Accounting System 1.0. This issue affects some unknown processing of the file /viewin_costumer.php of the component Parameter Handler. Such manipulation of the argument cos_id leads to sql injection. The attack can be launched remotely. The exploit has been disclosed publicly and may be used.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/30/2026, 20:23:34 UTC

Technical Analysis

CVE-2026-5150 is a SQL injection vulnerability identified in version 1.0 of the code-projects Accounting System. The flaw exists in the /viewin_costumer.php file within the Parameter Handler component, where the cos_id parameter is improperly sanitized or validated. This improper handling allows an attacker to inject arbitrary SQL commands remotely, without requiring authentication or user interaction. The vulnerability can be exploited by crafting malicious requests that manipulate the cos_id parameter to alter backend SQL queries, potentially exposing sensitive data, modifying database contents, or disrupting normal operations. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and low impact on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). The vulnerability has been publicly disclosed but no known exploits have been reported in the wild yet. The absence of patches or official fixes at the time of disclosure increases the urgency for organizations to implement compensating controls. The vulnerability primarily threatens the confidentiality and integrity of database information managed by the accounting system, which may include financial records, customer data, and transactional details. Given the critical nature of accounting data, exploitation could lead to financial fraud, data leakage, or operational disruptions.

Potential Impact

The SQL injection vulnerability in code-projects Accounting System 1.0 can have significant consequences for organizations relying on this software. Successful exploitation may allow attackers to extract sensitive financial and customer data, modify accounting records, or disrupt system availability. This could lead to financial losses, regulatory non-compliance, reputational damage, and operational downtime. Since the vulnerability requires no authentication and can be triggered remotely, the attack surface is broad, increasing the likelihood of exploitation especially after public disclosure. Organizations in sectors such as finance, retail, and services using this accounting system are particularly at risk. The medium severity rating reflects the moderate impact on confidentiality, integrity, and availability, but the ease of exploitation and lack of required privileges elevate the threat level. Additionally, the absence of known patches means organizations must rely on mitigations until an official fix is available.

Mitigation Recommendations

To mitigate CVE-2026-5150, organizations should first verify if they are running code-projects Accounting System version 1.0 and immediately restrict access to the /viewin_costumer.php endpoint, ideally limiting it to trusted internal networks. Implementing a Web Application Firewall (WAF) with rules to detect and block SQL injection attempts targeting the cos_id parameter can provide an effective temporary defense. Input validation and sanitization should be enforced at the application level, ensuring that cos_id accepts only expected numeric or predefined values. Monitoring and logging of suspicious requests to this endpoint should be enhanced to detect potential exploitation attempts early. Organizations should engage with the vendor for patches or updates and apply them promptly once available. Additionally, conducting regular security assessments and penetration testing focusing on SQL injection vectors will help identify and remediate similar vulnerabilities proactively. Backup critical accounting data regularly and ensure incident response plans are updated to handle potential data breaches.

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-03-30T13:27:33.863Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69cad830e6bfc5ba1d66dc17

Added to database: 3/30/2026, 8:08:16 PM

Last enriched: 3/30/2026, 8:23:34 PM

Last updated: 3/30/2026, 9:11:34 PM

Views: 4

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