Subscriber access to privileged automation actions
Published Jun 15, 2026 · Updated Jun 15, 2026
Broken authentication in FunnelKit Automations 3.7.3 and earlier allows remote authenticated users to invoke privileged automation actions. The 3.8.0 changelog identifies legacy automation actions as the hardened locus but does not disclose the faulty authentication operation. Subscriber access is required; public sources do not identify the reachable actions or the exact service-interruption consequence.
Summary
What happened
Broken authentication in FunnelKit Automations 3.7.3 and earlier allows remote authenticated users to invoke privileged automation actions. The 3.8.0 changelog identifies legacy automation actions as the hardened locus but does not disclose the faulty authentication operation. Subscriber access is required; public sources do not identify the reachable actions or the exact service-interruption consequence.
The record
- CVE
- CVE-2026-39450
- Published
- Jun 15, 2026
- Updated
- Jun 15, 2026
- Vendor
- FunnelKit
- Product
- FunnelKit Automations
- Classifications
- CWE-288, CAPEC-50
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 15, 2026CVE publishedPublication date reported by the CVE source.
- Jun 15, 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=n/a <=3.7.3 changes=[{"at":"3.8.0","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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