Feed access interruption via unauthorized token regeneration
Published Jan 2, 2023 · Updated Apr 10, 2025
Missing authorization in Syde GmbH Authenticator before 1.3.1 allows remote authenticated users to interrupt feed access by resetting its token. The regenerate_token AJAX action accepts a nonce exposed to subscribers and replaces the shared feed token without checking a privileged capability. Subscriber access and token-based feed authentication are required; regeneration invalidates the token shared with other feed consumers.
Summary
What happened
Missing authorization in Syde GmbH Authenticator before 1.3.1 allows remote authenticated users to interrupt feed access by resetting its token. The regenerate_token AJAX action accepts a nonce exposed to subscribers and replaces the shared feed token without checking a privileged capability. Subscriber access and token-based feed authentication are required; regeneration invalidates the token shared with other feed consumers.
The record
- CVE
- CVE-2022-3994
- Published
- Jan 2, 2023
- Updated
- Apr 10, 2025
- Vendor
- Syde GmbH
- Product
- Authenticator
- Classifications
- CWE-400, T1565
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 2, 2023CVE publishedPublication date reported by the CVE source.
- Apr 10, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.3.1
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.
Public exploit references
- WPScan regenerate_token proof of conceptproof of concept · 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