<?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/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>SoftNews Media Group - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/vendors/softnews-media-group/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Wed, 23 Sep 2026 22:46:52 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/vendors/softnews-media-group/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>SQL Injection in DataLife Engine Search Module</title><link>https://feed.craftedsignal.io/briefs/2026-09-datalife-sql-injection/</link><pubDate>Wed, 23 Sep 2026 22:46:52 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-09-datalife-sql-injection/</guid><description>DataLife Engine 18.0 contains a remote SQL injection vulnerability in the search module's strip_data function, allowing unauthorized database queries via the story argument.</description><content:encoded><![CDATA[<p>SoftNews Media Group DataLife Engine version 18.0 contains a high-severity SQL injection vulnerability identified as CVE-2026-96604. The flaw exists within the strip_data function located in engine/modules/search.php. An unauthenticated remote attacker can exploit this by injecting malicious SQL commands into the story argument processed by the search module. This vulnerability allows for unauthorized interaction with the underlying database, potentially leading to data exfiltration or administrative compromise of the web application. Publicly available exploit material increases the risk of opportunistic targeting. The vendor has not responded to disclosure efforts, leaving installations currently exposed without an official security patch.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows remote attackers to execute arbitrary SQL queries against the DataLife Engine database. This can result in the full disclosure of sensitive user data, credential theft, or unauthorized modification of web content. Given the public availability of exploit code, organizations running DataLife Engine 18.0 are at immediate risk of automated scanning and exploitation by threat actors.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Monitor web server logs for suspicious requests to engine/modules/search.php containing SQL syntax characters (e.g., UNION, SELECT, OR, --, ') within the story parameter.</li>
<li>Implement Web Application Firewall (WAF) rules to inspect and sanitize input directed at the search module's story argument.</li>
<li>Audit access to the database layer to identify any unexpected query patterns originating from the web application's search functionality.</li>
<li>Because the vendor has not provided a patch, consider implementing temporary input validation or sanitization patches at the application level to strip SQL metacharacters from the story parameter before processing.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>web-vulnerability</category><category>sql-injection</category><category>cve-2026-96604</category></item></channel></rss>