<?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>Piwigo — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/piwigo/</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, 03 Apr 2026 22:16:26 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/piwigo/feed.xml" rel="self" type="application/rss+xml"/><item><title>Piwigo SQL Injection Vulnerability (CVE-2026-27885)</title><link>https://feed.craftedsignal.io/briefs/2026-04-piwigo-sqli/</link><pubDate>Fri, 03 Apr 2026 22:16:26 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-piwigo-sqli/</guid><description>CVE-2026-27885 is a SQL Injection vulnerability in Piwigo before version 16.3.0, affecting the Activity List API endpoint, allowing an authenticated administrator to extract sensitive data.</description><content:encoded><![CDATA[<p>Piwigo is an open-source photo gallery application. A SQL Injection vulnerability, identified as CVE-2026-27885, exists in Piwigo versions prior to 16.3.0. Specifically, the Activity List API endpoint is susceptible. An authenticated administrator, by crafting malicious SQL queries, can exploit this vulnerability to extract sensitive data, including user credentials, email addresses, and all stored content within the Piwigo database. Piwigo versions 16.3.0 and later contain a patch for this vulnerability. This allows attackers to potentially take over the entire Piwigo instance by exploiting the vulnerability and dumping the credentials of other administrators or users. The CVSS v3.1 base score is rated as 7.2 (HIGH).</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains administrative access to a Piwigo instance running a version prior to 16.3.0, through either brute-forcing credentials or compromising an existing admin account.</li>
<li>The attacker crafts a malicious SQL query designed to exploit the SQL Injection vulnerability in the Activity List API endpoint.</li>
<li>The attacker sends a request to the vulnerable Activity List API endpoint with the crafted SQL payload embedded within the request parameters.</li>
<li>The Piwigo application processes the request without proper sanitization, executing the malicious SQL query against the database.</li>
<li>The database returns the results of the malicious query, which could include sensitive information such as user credentials, email addresses, and other stored data.</li>
<li>The attacker captures the database response and extracts the sensitive information.</li>
<li>The attacker uses the extracted credentials to elevate privileges or impersonate other users, potentially gaining full control of the Piwigo instance.</li>
<li>The attacker exfiltrates sensitive data, defaces the photo gallery, or performs other malicious actions.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-27885 can lead to complete compromise of a Piwigo instance. An attacker could steal user credentials, modify or delete photos, and potentially use the compromised server as a staging point for further attacks. The number of affected installations is unknown, but any Piwigo instance running a version prior to 16.3.0 is vulnerable if an attacker can get administrative access.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade Piwigo installations to version 16.3.0 or later to patch CVE-2026-27885.</li>
<li>Monitor web server logs for suspicious requests to the Activity List API endpoint that contain potentially malicious SQL syntax to trigger the rule <code>Detecting SQL Injection Attempts in Piwigo</code>.</li>
<li>Implement strict input validation and sanitization on all user-supplied data to prevent SQL injection vulnerabilities.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>sql-injection</category><category>web-application</category><category>piwigo</category></item><item><title>Piwigo SQL Injection Vulnerability (CVE-2026-27834)</title><link>https://feed.craftedsignal.io/briefs/2026-04-piwigo-sql-injection/</link><pubDate>Fri, 03 Apr 2026 22:16:26 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-piwigo-sql-injection/</guid><description>A SQL Injection vulnerability (CVE-2026-27834) exists in Piwigo versions prior to 16.3.0, allowing authenticated administrators to execute arbitrary SQL commands via the pwg.users.getList Web Service API method.</description><content:encoded><![CDATA[<p>Piwigo, an open-source photo gallery application, is vulnerable to SQL injection in versions before 16.3.0. The vulnerability resides in the <code>pwg.users.getList</code> Web Service API method.  Specifically, the <code>filter</code> parameter is directly concatenated into a SQL query without sufficient sanitization. This allows an authenticated administrator to inject and execute arbitrary SQL commands on the Piwigo server.  Successful exploitation could lead to data exfiltration, modification, or complete compromise of the Piwigo instance.  Version 16.3.0 patches this vulnerability. The vulnerability was reported on April 3rd, 2026.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An authenticated administrator logs into the Piwigo web interface.</li>
<li>The administrator crafts a malicious HTTP POST request to the <code>api.php</code> endpoint, targeting the <code>pwg.users.getList</code> Web Service API method.</li>
<li>The malicious request includes the <code>filter</code> parameter containing a SQL injection payload. The payload is designed to exploit the lack of sanitization.</li>
<li>The Piwigo application receives the request and processes the <code>pwg.users.getList</code> API call.</li>
<li>The application concatenates the attacker-controlled <code>filter</code> parameter directly into a SQL query without proper escaping or sanitization.</li>
<li>The crafted SQL query is executed against the Piwigo database.</li>
<li>The injected SQL code performs unauthorized actions, such as extracting sensitive data, modifying database records, or executing system commands via SQL.</li>
<li>The attacker retrieves the results of the injected SQL query from the HTTP response.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this SQL injection vulnerability (CVE-2026-27834) in Piwigo versions before 16.3.0 can lead to complete compromise of the Piwigo installation. An attacker could potentially access sensitive data such as user credentials, private photos, and system configuration information. The attacker could also modify or delete data, disrupt service, or potentially gain unauthorized access to the underlying server. Given the administrator privilege required for exploitation, the impact is considered significant within the vulnerable Piwigo instance.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade Piwigo to version 16.3.0 or later to patch CVE-2026-27834 (see references).</li>
<li>Deploy the provided Sigma rule to detect exploitation attempts against the <code>pwg.users.getList</code> API endpoint.</li>
<li>Monitor web server logs for suspicious POST requests to <code>api.php</code> containing unusual characters or SQL keywords in the <code>filter</code> parameter.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>piwigo</category><category>sql-injection</category><category>cve-2026-27834</category></item><item><title>Piwigo Unauthenticated History Search Access</title><link>https://feed.craftedsignal.io/briefs/2026-04-piwigo-history-search/</link><pubDate>Fri, 03 Apr 2026 22:16:25 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-piwigo-history-search/</guid><description>Piwigo versions prior to 16.3.0 expose the full browsing history of gallery visitors to unauthenticated users via the pwg.history.search API method due to a missing authorization check.</description><content:encoded><![CDATA[<p>Piwigo, an open-source photo gallery application, contains a vulnerability (CVE-2026-27833) affecting versions prior to 16.3.0. The vulnerability lies within the <code>pwg.history.search</code> API method, which lacks an <code>admin_only</code> access control. This oversight allows unauthenticated users to query and retrieve the browsing history of all gallery visitors. An attacker can leverage this flaw to gain insights into user behavior, potentially exposing sensitive information about their interests and activities within the photo gallery. Piwigo version 16.3.0 addresses this vulnerability by implementing the necessary authorization check.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An unauthenticated attacker identifies a Piwigo instance running a version prior to 16.3.0.</li>
<li>The attacker crafts a malicious HTTP request targeting the <code>pwg.history.search</code> API endpoint.</li>
<li>The attacker sends the crafted HTTP request to the vulnerable Piwigo server.</li>
<li>The Piwigo server, lacking proper authorization checks, processes the request without authentication.</li>
<li>The server retrieves the browsing history of all gallery visitors from the database.</li>
<li>The server returns the browsing history data in the HTTP response to the attacker.</li>
<li>The attacker parses the response and analyzes the browsing history data to identify user activities and interests.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-27833 allows unauthenticated attackers to access sensitive user browsing history within a Piwigo photo gallery. This can lead to a privacy breach, potentially exposing user interests, activities, and even personal information gleaned from their browsing patterns. The impact is limited to information disclosure as the attacker cannot modify data, but the privacy implications can be significant for users of affected Piwigo installations.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade all Piwigo installations to version 16.3.0 or later to patch CVE-2026-27833.</li>
<li>Monitor web server logs for requests to the <code>pwg.history.search</code> API endpoint, especially those lacking authentication, to detect potential exploitation attempts. Deploy the Sigma rule <code>Detect Piwigo History Search Access</code> to identify suspicious activity.</li>
<li>Implement a Web Application Firewall (WAF) rule to block unauthorized access to the <code>pwg.history.search</code> API endpoint.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>piwigo</category><category>vulnerability</category><category>information-disclosure</category></item></channel></rss>