Unauthorized tag creation via missing CSRF token
Published May 23, 2023 · Updated Jan 31, 2025
Cross-site request forgery in Piwigo 13.6.0 allows remote attackers to add tags through an administrator's authenticated browser. The backend add-tags handler accepts a state-changing form submission without requiring a CSRF token and creates the supplied tag. A logged-in administrator must visit attacker-controlled content; the demonstrated consequence is unauthorized tag creation.
Summary
What happened
Cross-site request forgery in Piwigo 13.6.0 allows remote attackers to add tags through an administrator's authenticated browser. The backend add-tags handler accepts a state-changing form submission without requiring a CSRF token and creates the supplied tag. A logged-in administrator must visit attacker-controlled content; the demonstrated consequence is unauthorized tag creation.
The record
- CVE
- CVE-2023-33359
- Published
- May 23, 2023
- Updated
- Jan 31, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 23, 2023CVE publishedPublication date reported by the CVE source.
- Jan 31, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Add-tags CSRF proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo