Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with upload rights
-
DeliveryUpload SVG-disguised-as-PNG image
-
ExploitImagick parses embedded SVG/MSL
-
ExecutionRead local files or write attacker files
-
ImpactAchieve code execution (config-dependent)
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
|
| Exploitation Conditions | Requires (1) Piwigo configured to use the Imagick/ImageMagick library for image processing rather than the GD backend; (2) an authenticated account with image-upload permission (vendor rates PR:H/admin, but upload rights may be broader); and (3) for the arbitrary file read, only that Imagick renders SVG delegates on the crafted upload. Escalation to file write / RCE additionally requires a permissive ImageMagick policy.xml that allows MSL and SVG/coder delegates - often restricted or disabled in hardened installs, which is the primary limiting factor. No user interaction beyond the attacker's own upload is needed (UI:N). |
| Impact | The vendor CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H = 7.2) frames this as an authenticated, network-reachable flaw with full C/I/A impact. That impact profile is only partly reliable: the description confirms arbitrary file read via SVG/PNG format confusion (solidly C:H), but the file-write and remote-code-execution outcomes are explicitly qualified as occurring 'depending on configuration' and via ImageMagick's Magick Scripting Language (MSL) - a delegate path that modern ImageMagick installs frequently disable through policy.xml. So the I:H/A:H (and the RCE tag) represent a plausible worst case, not a guaranteed default outcome, and I:L/A:L is the more honest baseline for a default deployment. There is no EPSS score, no CISA KEV listing, and no public POC referenced, so exploitation is theoretical/analytical at this stage. Two signals warrant verification: (1) the vendor rates PR:H (implying admin), but image upload in Piwigo is often available to lower-privileged authenticated users, so real privilege requirement may be PR:L; (2) the whole attack is gated on Piwigo using the Imagick library (not the GD backend) - a configuration-dependent prerequisite that materially narrows the exposed population. Net: a genuine authenticated flaw worth patching, but not an unauthenticated internet-mass-exploitation priority. |
| Exploit ScenarioDerived | An authenticated Piwigo user with image-upload rights, on an instance configured to use the Imagick library, uploads a file that disguises SVG content as a PNG; when Imagick processes it, embedded SVG elements referencing local files cause server-side file disclosure (e.g., configuration or credential files). In an instance whose ImageMagick delegate/MSL policy is permissive, the attacker escalates to attacker-controlled MSL instructions to write files and achieve remote code execution. No public exploit code is referenced at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 25, 2026
Image upload handling in Piwigo before 16.4.0 permits authenticated attackers to read arbitrary files and, in permissive configurations, write server-side files or achieve remote code execution by abusing Imagick's processing of user-supplied images. Format confusion-such as disguising SVG content as PNG-can trick Imagick into interpreting embedded SVG elements that reference local files, while the Magick Scripting Language (MSL) may be abused for unauthorized file writes and code execution if ImageMagick's policy.xml allows MSL and SVG delegates. Exploitation requires Piwigo to use the Imagick backend (not GD) and an authenticated account with upload rights; vendor rates it 7.2 with PR:H and full C/I/A impact, whereas independent assessment lowers integrity/availability to L and stresses that hardened ImageMagick policies commonly block the RCE path. No public exploit identified at time of analysis, and version 16.4.0 provides the vendor-released patch.
RemediationAI
Upgrade Piwigo to version 16.4.0 or later, the vendor-released patch (see https://github.com/Piwigo/Piwigo/security/advisories/GHSA-j9q6-q52g-g8jw ). If immediate upgrading is not possible, switch Piwigo's image backend from Imagick to GD in the administration settings, which eliminates the vulnerable code path at the cost of some image-processing features (e.g., advanced format support, better quality thumbnails). Alternatively, harden ImageMagick by editing policy.xml to disable the MSL coder and the SVG, MSL, and URL coders for upload processing; this blocks the file-write and RCE escalation but does not prevent SVG-based file read unless all SVG delegate handling is disabled, which may break legitimate SVG uploads. Restrict image-upload permission to trusted roles only, since the attack requires an authenticated uploader, and monitor for unusual file reads by the web server user. Additional independent analysis is available at https://www.helx.io/en/blog/advisory-piwigo . Note that vendor CVSS rates impact as full C/I/A with PR:H, while independent assessment assesses C:H/I:L/A:L and PR:L, reflecting that hardened policy.xml configurations-the primary limiting factor-often reduce the practical impact.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw resides in Piwigo's image-upload processing pipeline when it delegates image handling to the Imagick PHP extension, which in turn invokes ImageMagick's decoders and delegates. CWE-20 (Improper Input Validation) is the root cause: Piwigo does not sufficiently validate the uploaded file's actual content against its declared type, so an attacker can supply a file that appears to be a PNG but contains SVG markup. ImageMagick's SVG delegate then processes the embedded SVG, which can include external entity references or file-reading directives (e.g., xlink:href to file:///etc/passwd), yielding arbitrary file read. More severely, if ImageMagick's policy.xml does not restrict the MSL coder, an attacker can submit MSL instructions that write files to the server and execute code. The CPE string cpe:2.3:a:piwigo:piwigo:*:*:*:*:*:*:*:* identifies all versions of Piwigo before the fixed 16.4.0 release as affected. The need for the Imagick backend (rather than GD) and a permissive ImageMagick policy are the key environmental preconditions that determine whether the vulnerability is limited to file read or escalates to RCE.
Know when Piwigo gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Authenticated upload rights (PR:L) and network reach; reliable arbitrary file read (C:H), but file-write/RCE are Imagick-MSL-config-dependent so I:L/A:L rather than H.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
DescriptionCVE.org
Piwigo before v16.4.0 is vulnerable to arbitrary file read and remote code execution in image upload handling when using the Imagick library due to insufficient validation and unsafe processing of user-supplied image files. By abusing format confusion (e.g., disguising SVG content as PNG), an attacker can trigger unintended interpretation of embedded SVG elements that reference local files. In more advanced scenarios, the Imagick support for Magick Scripting Language (MSL) may be abused to process attacker-controlled instructions, potentially leading to unauthorized server-side file writes and remote code execution, depending on configuration. This has been patched in 16.4.0.
Technical POC Analysis
CWE-20 (Improper Input Validation) in Piwigo's image upload handling.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
Piwigo, an open-source image management platform, is affected by a high-severity vulnerability (CVE-2026-85750) that enables authenticated users with upload privileges to read arbitrary server files and, in permissive ImageMagick configurations, write files or execute remote code. Vendor-released patch: 16.4.0. No public exploit identified at time of analysis, but the potential for data exposure or server compromise means leadership should ensure all instances are patched and ImageMagick policies are hardened.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Directory traversal vulnerability in install.php in Piwigo before 2.4.7 allows remote attackers to read and delete arbit
Cross-site request forgery (CSRF) vulnerability in the LocalFiles Editor plugin in Piwigo before 2.4.7 allows remote att
SQL injection vulnerability in the administrative backend in Piwigo through 2.9.1 allows remote users to execute arbitra
Piwigo 13.6.0 is vulnerable to SQL Injection via in the "profile" function. Rated critical severity (CVSS 9.8), this vul
Piwigo 13.6.0 is vulnerable to SQL Injection via /admin/permalinks.php. Rated critical severity (CVSS 9.8), this vulnera
Piwigo 11.4.0 allows admin/user_list_backend.php order[0][dir] SQL Injection. Rated critical severity (CVSS 9.8), this v
admin.php?page=account_billing in Piwigo 2.9.5 has XSS via the vat_number, billing_name, company, or billing_
admin.php?page=notification_by_mail in Piwigo 2.9.5 has XSS via the nbm_send_html_mail, nbm_send_mai
Cross-site request forgery (CSRF) vulnerability in Piwigo through 2.9.1 allows remote attackers to hijack the authentica
Cross-site request forgery (CSRF) vulnerability in Piwigo through 2.9.1 allows remote attackers to hijack the authentica
Cross-site request forgery (CSRF) vulnerability in Piwigo through 2.9.1 allows remote attackers to hijack the authentica
admin/configuration.php in Piwigo 2.9.2 has CSRF. Rated high severity (CVSS 8.8), this vulnerability is remotely exploit
EUVD-2026-87094
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB