Stored comment manipulation via unchecked content identifier
Published Nov 7, 2023 · Updated Sep 4, 2024
Improper access control in Microweber before 2.0.0 allows remote authenticated users to attach comments to inactive or deleted content. UserCommentReplyComponent::save trusted the client-supplied state.rel_id and created the comment without verifying that the referenced content existed and was active. Low-privilege access to the comment interface is required, and successful exploitation alters stored comment relationships rather than granting administrative control.
Summary
What happened
Improper access control in Microweber before 2.0.0 allows remote authenticated users to attach comments to inactive or deleted content. UserCommentReplyComponent::save trusted the client-supplied state.rel_id and created the comment without verifying that the referenced content existed and was active. Low-privilege access to the comment interface is required, and successful exploitation alters stored comment relationships rather than granting administrative control.
The record
- CVE
- CVE-2023-5976
- Published
- Nov 7, 2023
- Updated
- Sep 4, 2024
- Vendor
- Microweber
- Product
- Microweber
- Classifications
- CWE-284
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 7, 2023CVE publishedPublication date reported by the CVE source.
- Sep 4, 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=0 <2.0
- Affected versionversion=unspecified <2.0
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