CVE Alert: CVE-2025-2415 – Akinsoft – MyRezzta

CVE-2025-2415

HIGHNo exploitation known

Improper Restriction of Excessive Authentication Attempts vulnerability in Akinsoft MyRezzta allows Authentication Bypass.This issue affects MyRezzta: from s2.03.01 before v2.05.01.

CVSS v3.1 (8.6)
AV NETWORK · AC LOW · PR NONE · UI NONE · S UNCHANGED
Vendor
Akinsoft
Product
MyRezzta
Versions
s2.03.01 lt v2.05.01
CWE
CWE-307, CWE-307 Improper Restriction of Excessive Authentication Attempts
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
Published
2025-09-03T08:54:31.583Z
Updated
2025-09-03T14:37:26.089Z

AI Summary Analysis

**Risk verdict** High risk due to an OTP-based authentication bypass allowing remote access; exploitation is not known to be active at present, but patching should be pursued promptly.

**Why this matters** The vulnerability enables unauthenticated access to protected resources, potentially exposing sensitive data or enabling administrative actions. Its network-facing nature and high confidentiality impact mean a successful bypass could have outsized business consequences, even before widespread exploitation.

**Most likely attack path** Attacker can reach the authentication endpoint over the network without user interaction or privileges, and trigger the bypass remotely. If successful, they gain unauthorised access and could pivot to other systems or data.

**Who is most exposed** Organisations exposing the authentication interface to the internet or running older revisions prior to the fixed release are at highest risk.

Detection ideas

  • Look for authentication successes that occur without the expected OTP or 2FA events being triggered.
  • Monitor for spikes in login attempts from diverse or unusual geographies without corresponding legitimate activity.
  • Audit logs for anomalous sequences or admin-level accounts accessed without standard MFA prompts.
  • Correlate sudden, unusual access times with elevated entitlement accounts.
  • Validate that OTP/2FA enforcement is consistently applied across all login paths.

Mitigation and prioritisation

  • Apply the vendor patch to v2.05.01 or newer as a top priority; plan rapid rollout.
  • Enforce strong MFA on all accounts and disable any bypass configuration in the OTP flow.
  • Implement rate limiting, account lockouts, and WAF rules on the authentication endpoint.
  • Inventory affected deployments, schedule testing in a staging environment, and establish a clear change-management plan.
  • If patch timing is constrained, implement compensating controls such as IP allowlisting for the login portal and network segmentation to limit exposure.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on “Patreon” or “Buy Me A Coffee” using the buttons below

To keep up to date follow us on the below channels.