<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Itsourcecode — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/vendors/itsourcecode/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Fri, 01 May 2026 20:16:24 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/vendors/itsourcecode/feed.xml" rel="self" type="application/rss+xml"/><item><title>SQL Injection Vulnerability in itsourcecode Courier Management System</title><link>https://feed.craftedsignal.io/briefs/2026-05-courier-mgmt-sqli/</link><pubDate>Fri, 01 May 2026 20:16:24 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-courier-mgmt-sqli/</guid><description>itsourcecode Courier Management System 1.0 is vulnerable to SQL Injection via the ID parameter in /edit_staff.php, potentially allowing remote attackers to execute arbitrary SQL commands.</description><content:encoded><![CDATA[<p>itsourcecode Courier Management System 1.0 is vulnerable to a SQL injection vulnerability. The vulnerability resides in the <code>/edit_staff.php</code> file and can be exploited by manipulating the <code>ID</code> argument. This allows a remote attacker to inject malicious SQL queries, potentially leading to unauthorized data access, modification, or deletion. The exploit is publicly available, increasing the risk of exploitation. The vulnerability was reported on May 1, 2026, and affects version 1.0 of the Courier Management System.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker identifies the <code>/edit_staff.php</code> endpoint in the Courier Management System 1.0.</li>
<li>The attacker crafts a malicious SQL injection payload within the <code>ID</code> parameter of a HTTP GET or POST request.</li>
<li>The attacker sends the crafted request to the <code>/edit_staff.php</code> endpoint.</li>
<li>The application fails to properly sanitize the <code>ID</code> parameter, allowing the SQL injection payload to be processed by the database.</li>
<li>The injected SQL query is executed against the database, potentially allowing the attacker to bypass authentication or authorization controls.</li>
<li>The attacker retrieves sensitive information from the database, such as user credentials, financial records, or other confidential data.</li>
<li>The attacker modifies data in the database, potentially altering application behavior or causing data corruption.</li>
<li>The attacker gains full control of the database server.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this SQL injection vulnerability could allow attackers to read, modify, or delete sensitive data within the Courier Management System database. This could lead to unauthorized access to customer information, financial data, and other confidential records. Given the public availability of the exploit, organizations using Courier Management System 1.0 are at a high risk of compromise.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Apply input validation and sanitization to the <code>ID</code> parameter in <code>/edit_staff.php</code> to prevent SQL injection (CVE-2026-7592).</li>
<li>Deploy the provided Sigma rule to detect potential SQL injection attempts targeting the <code>/edit_staff.php</code> endpoint.</li>
<li>Implement a web application firewall (WAF) rule to block known SQL injection payloads (CVE-2026-7592).</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>sql-injection</category><category>web-application</category><category>cve</category></item><item><title>itsourcecode Construction Management System SQL Injection Vulnerability</title><link>https://feed.craftedsignal.io/briefs/2026-04-construction-management-sql-injection/</link><pubDate>Mon, 27 Apr 2026 02:16:01 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-construction-management-sql-injection/</guid><description>A SQL injection vulnerability exists in itsourcecode Construction Management System version 1.0, affecting the processing of the /locations.php file, allowing a remote attacker to inject SQL commands by manipulating the 'address' argument, with a publicly available exploit.</description><content:encoded><![CDATA[<p>A SQL injection vulnerability has been identified in itsourcecode Construction Management System version 1.0. The vulnerability resides within the <code>/locations.php</code> file and is triggered by manipulating the <code>address</code> argument. This allows a remote attacker to inject arbitrary SQL commands into the application&rsquo;s database queries. This poses a significant risk as successful exploitation could lead to unauthorized data access, modification, or deletion, potentially compromising the entire system. The vulnerability has been assigned CVE-2026-7075, and a public exploit is available, increasing the likelihood of exploitation.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker identifies an instance of itsourcecode Construction Management System 1.0.</li>
<li>Attacker sends a crafted HTTP request to <code>/locations.php</code> with a malicious SQL payload embedded in the <code>address</code> parameter.</li>
<li>The application fails to properly sanitize the <code>address</code> parameter.</li>
<li>The unsanitized input is incorporated into an SQL query.</li>
<li>The database executes the attacker-controlled SQL query.</li>
<li>The attacker extracts sensitive data from the database.</li>
<li>Attacker may use the injected queries to modify or delete data.</li>
<li>The attacker compromises the confidentiality, integrity, and availability of the Construction Management System.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this SQL injection vulnerability (CVE-2026-7075) can lead to unauthorized access to sensitive data, including user credentials, financial records, and project details stored within the Construction Management System database. Attackers could potentially modify or delete critical data, disrupt business operations, or gain complete control over the application and its underlying infrastructure. Given the public availability of the exploit, organizations using the affected version of itsourcecode Construction Management System are at immediate risk.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the provided Sigma rule to detect suspicious HTTP requests to <code>/locations.php</code> containing potentially malicious SQL syntax in the <code>cs-uri-query</code> (webserver logs).</li>
<li>Implement input validation and sanitization for the <code>address</code> parameter in <code>/locations.php</code> to prevent SQL injection attacks.</li>
<li>Monitor web server logs for unusual activity, especially requests targeting <code>/locations.php</code> with long or complex <code>address</code> parameters.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>sql-injection</category><category>web-application</category><category>cve-2026-7075</category></item><item><title>itsourcecode Electronic Judging System SQL Injection Vulnerability (CVE-2026-7555)</title><link>https://feed.craftedsignal.io/briefs/2024-01-electronic-judging-sql-injection/</link><pubDate>Wed, 03 Jan 2024 18:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-electronic-judging-sql-injection/</guid><description>A remote SQL injection vulnerability (CVE-2026-7555) exists in itsourcecode Electronic Judging System 1.0 via manipulation of the Username argument in the /intrams/login.php file, potentially leading to unauthorized data access and modification.</description><content:encoded><![CDATA[<p>itsourcecode Electronic Judging System 1.0 is vulnerable to SQL injection in the /intrams/login.php file. The vulnerability, identified as CVE-2026-7555, allows a remote attacker to inject malicious SQL code by manipulating the <code>Username</code> argument. The vulnerability was reported on 2026-05-01. Successful exploitation could lead to unauthorized access to sensitive data, modification of existing data, or even complete compromise of the database. The availability of a public exploit increases the risk of widespread exploitation. This poses a significant threat to organizations using the affected judging system, potentially disrupting operations and compromising confidential information.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker identifies an instance of itsourcecode Electronic Judging System 1.0 running on a target server.</li>
<li>The attacker crafts a malicious HTTP POST request targeting the <code>/intrams/login.php</code> endpoint.</li>
<li>Within the POST request, the attacker manipulates the <code>Username</code> parameter with a SQL injection payload.</li>
<li>The server-side application improperly processes the attacker-supplied <code>Username</code> value, failing to sanitize special characters.</li>
<li>The unsanitized <code>Username</code> value is incorporated into a SQL query executed against the application database.</li>
<li>The injected SQL code modifies the query&rsquo;s intended logic, potentially bypassing authentication or extracting sensitive data.</li>
<li>The database server executes the modified SQL query, returning the results to the web application.</li>
<li>The attacker gains unauthorized access to sensitive information, such as user credentials, judging data, or other confidential application data.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this SQL injection vulnerability could allow attackers to bypass authentication, gain access to sensitive judging data, modify existing records, or potentially gain complete control of the database server. This could lead to data breaches, financial loss, reputational damage, and disruption of judging events. The lack of specific victim count or sector information in the source data makes quantifying the exact impact challenging.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Apply appropriate input validation and sanitization techniques to the <code>Username</code> parameter in <code>/intrams/login.php</code> to mitigate the SQL injection vulnerability.</li>
<li>Deploy the Sigma rule <code>Detect Suspicious Login Attempts via SQL Injection</code> to detect exploitation attempts targeting <code>/intrams/login.php</code>.</li>
<li>Monitor web server logs for suspicious POST requests containing unusual characters or SQL keywords in the <code>Username</code> parameter.</li>
<li>Consider implementing a web application firewall (WAF) with rules to block common SQL injection patterns.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>sql-injection</category><category>vulnerability</category><category>web-application</category></item></channel></rss>