Article modification via tokenless cross-origin requests
Published Dec 8, 2022 · Updated Apr 15, 2025
Cross-site request forgery in DuxCMS 2.1 allows remote attackers to modify articles through an authenticated administrator's browser. The article add and edit handlers accept cross-origin POST requests without an anti-CSRF token, including content and status fields. An administrator must be logged in and induced to submit the crafted page; successful exploitation creates or alters published content.
Summary
What happened
Cross-site request forgery in DuxCMS 2.1 allows remote attackers to modify articles through an authenticated administrator's browser. The article add and edit handlers accept cross-origin POST requests without an anti-CSRF token, including content and status fields. An administrator must be logged in and induced to submit the crafted page; successful exploitation creates or alters published content.
The record
- CVE
- CVE-2020-36610
- Published
- Dec 8, 2022
- Updated
- Apr 15, 2025
- Vendor
- DuxCMS Project
- Product
- DuxCMS
- Classifications
- CWE-863, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 8, 2022CVE publishedPublication date reported by the CVE source.
- Apr 15, 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=2.1
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.
Public exploit references
- Add article has CSRF and XSS 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