Unauthenticated ticket reply injection via unprotected route
Published Aug 24, 2026 · Updated Aug 24, 2026
Missing authentication in Faveo Helpdesk 2.0.0 through 2.0.3 allows remote attackers to inject replies into arbitrary ticket threads. The post-ticket-reply route sits outside the authentication middleware, and post_ticket_reply writes a thread row under the original owner's user ID. No account or user interaction is required; knowing or guessing a sequential ticket number is enough to write attacker-controlled content under the owner's identity.
Summary
What happened
Missing authentication in Faveo Helpdesk 2.0.0 through 2.0.3 allows remote attackers to inject replies into arbitrary ticket threads. The post-ticket-reply route sits outside the authentication middleware, and post_ticket_reply writes a thread row under the original owner's user ID. No account or user interaction is required; knowing or guessing a sequential ticket number is enough to write attacker-controlled content under the owner's identity.
The record
- CVE
- CVE-2026-78434
- Published
- Aug 24, 2026
- Updated
- Aug 24, 2026
- Vendor
- Ladybird Web Solution Pvt. Ltd.
- Product
- Faveo Helpdesk
- Classifications
- CWE-306, CWE-287, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 24, 2026CVE publishedPublication date reported by the CVE source.
- Aug 24, 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=2.0.0
- Affected versionversion=2.0.1
- Affected versionversion=2.0.2
- Affected versionversion=2.0.3
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
- GitHub issue #8346 proof of conceptfunctional · 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