Quick answers
- Is CVE-2025-56224 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-56224 being exploited in the wild.
- How severe is CVE-2025-56224?
- High severity, with a CVSS score of 8.1, published 20 October 2025.
- Which products and versions are affected?
- Ascertia Signinghub <= 8.6.8.
- Is there a fix for CVE-2025-56224?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2025-56224 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2025-56224?
- Check whether you run Ascertia Signinghub at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is classified as CWE-307 (Improper Restriction of Excessive Authentication Attempts) within the mobile number verification function of SigningHub. The OTP verification endpoint fails to implement rate limiting or account lockout mechanisms after multiple failed attempts. A remote attacker can exploit this by automating a high volume of OTP guesses in rapid succession to successfully verify a mobile number without knowing the actual code. This bypasses a critical identity verification step. The issue is reported to be fixed in versions subsequent to 8.6.8.
Affected products
- Ascertia SigningHub <= 8.6.8
Timeline
- 2025-10-20: disclosed
- 2025-10-20: advisory