Unauthorized edits via missing CSRF token validation
Published Feb 20, 2023 · Updated Nov 25, 2024
Cross-site request forgery in Arnold Lesikar Submit By Mail 1.0b2.9 allows remote attackers to trigger edit_list.php actions. The handler reads the eid query parameter and proceeds without calling phpList's verifyCsrfGetToken request-token validator. Exploitation requires user interaction that causes an authenticated browser to submit the crafted request; the reported consequence is unauthorized modification only.
Summary
What happened
Cross-site request forgery in Arnold Lesikar Submit By Mail 1.0b2.9 allows remote attackers to trigger edit_list.php actions. The handler reads the eid query parameter and proceeds without calling phpList's verifyCsrfGetToken request-token validator. Exploitation requires user interaction that causes an authenticated browser to submit the crafted request; the reported consequence is unauthorized modification only.
The record
- CVE
- CVE-2015-10081
- Published
- Feb 20, 2023
- Updated
- Nov 25, 2024
- Vendor
- Arnold Lesikar
- Product
- Submit By Mail
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 20, 2023CVE publishedPublication date reported by the CVE source.
- Nov 25, 2024Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0b2.9
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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