CVE-2026-57945: photoprism · Insecure Direct Object Reference
Affects photoprismSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 260601-a7d098548 when convenient.
Data as of 8 Nov 2026, 14:36 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 5.3 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 4.3 |
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-07-01.
- Patch
- Available – fixed in 260601-a7d098548
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 29 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Upgrade photoprism to 260601-a7d098548.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| photoprismphotoprism | Affected
| Fixed in
|
GitHubphotoprismpkg:github/photoprismOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade PhotoPrism to version 260601-a7d098548 or later, where this access control vulnerability has been fixed. No additional mitigation steps are required once the official fix is applied.
Description
PhotoPrism versions before 260601-a7d098548 contain an access control vulnerability allowing authenticated non-admin users to modify other users' profile information. This occurs due to missing session-to-user identifier validation in the PUT users API endpoint, enabling unauthorized profile overwrites.