Account and configuration changes via missing CSRF validation
Published Apr 28, 2023 · Updated Jan 30, 2025
CSRF in chshcms mccms 2.6.3 allows remote attackers to trigger account, balance, and configuration changes through a user's browser. The front-end user-information and administrative actions accept state-changing requests without a CSRF token or Referer validation. An authenticated user must be induced to submit the forged request; an administrative session exposes administrator creation, user-balance changes, and site-configuration changes.
Summary
What happened
CSRF in chshcms mccms 2.6.3 allows remote attackers to trigger account, balance, and configuration changes through a user's browser. The front-end user-information and administrative actions accept state-changing requests without a CSRF token or Referer validation. An authenticated user must be induced to submit the forged request; an administrative session exposes administrator creation, user-balance changes, and site-configuration changes.
The record
- CVE
- CVE-2023-29815
- Published
- Apr 28, 2023
- Updated
- Jan 30, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 28, 2023CVE publishedPublication date reported by the CVE source.
- Jan 30, 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.
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