State changes via forged authenticated requests
Published Dec 19, 2023 · Updated Feb 25, 2026
Cross-site request forgery in Efacec BCU 500 4.07 allows remote attackers to trigger state-changing requests through a victim's session. Efacec has not published the affected endpoint or the missing request-validation operation that accepts the forged requests. Exploitation requires an authenticated user to open attacker-controlled content; an administrative victim permits compromise of the web application.
Summary
What happened
Cross-site request forgery in Efacec BCU 500 4.07 allows remote attackers to trigger state-changing requests through a victim's session. Efacec has not published the affected endpoint or the missing request-validation operation that accepts the forged requests. Exploitation requires an authenticated user to open attacker-controlled content; an administrative victim permits compromise of the web application.
The record
- CVE
- CVE-2023-6689
- Published
- Dec 19, 2023
- Updated
- Feb 25, 2026
- Vendor
- Efacec
- Product
- BCU 500
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 19, 2023CVE publishedPublication date reported by the CVE source.
- Feb 25, 2026Record 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=version 4.07
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