Unauthorized user edits via cross-user CSRF token
Published Nov 18, 2025 · Updated Dec 5, 2025
Cross-site request forgery in Windu CMS 4.1 before build 2250 allows remote attackers to submit unauthorized user-editing requests. The user-editing handler accepts a CSRF token issued to a different account instead of binding the token to the victim session. Open registration lets an attacker obtain a valid token, but exploitation still requires an authenticated victim to trigger the forged request; the specific editable fields are undisclosed.
Summary
What happened
Cross-site request forgery in Windu CMS 4.1 before build 2250 allows remote attackers to submit unauthorized user-editing requests. The user-editing handler accepts a CSRF token issued to a different account instead of binding the token to the victim session. Open registration lets an attacker obtain a valid token, but exploitation still requires an authenticated victim to trigger the forged request; the specific editable fields are undisclosed.
The record
- CVE
- CVE-2025-59110
- Published
- Nov 18, 2025
- Updated
- Dec 5, 2025
- Vendor
- JCD.PL
- Product
- Windu CMS
- Classifications
- CWE-352, CAPEC-62
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 18, 2025CVE publishedPublication date reported by the CVE source.
- Dec 5, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=4.1 changes=[{"at":"build 2250","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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