dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2024-13063

MEDIUM · 6.8 CVSS v3.1 Published 2025-09-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Authorization Bypass Through User-Controlled Key vulnerability in Akinsoft MyRezzta allows Forceful Browsing. This issue affects MyRezzta: from s2.02.02 before v2.05.01.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Authorization bypass vulnerability in Akinsoft MyRezzta allows attackers to manipulate user-controlled keys to perform forceful browsing and access resources outside their authorized scope. The vulnerability affects versions s2.02.02 through before v2.05.01.

MitigationImplement proper server-side authorization checks that validate user permissions before granting access to resources, ensuring user-controlled keys cannot be exploited to bypass access controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed MyRezzta version
    Locate the version information for Akinsoft MyRezzta in the application (typically found in the software itself, an about page, or configuration files within the installation directory)
    Affected if The installed version falls within s2.02.02 through before v2.05.01
  2. Compare version to affected range
    Review the identified version against the vulnerable range: s2.02.02 <= version < v2.05.01
    Affected if The installed version is within this range, meaning the authorization bypass is present
  3. Inspect authorization mechanism for user-controlled keys
    Examine the application's authentication and authorization logic to determine if user-supplied input (such as URL parameters, cookies, or headers) is being used directly as keys or identifiers to access resources without proper validation
    Affected if User-controlled keys are used in the authorization flow without server-side permission validation, enabling forceful browsing
  4. Verify access control scope
    Test whether users can access resources outside their authorized scope by manipulating identifiers or keys in requests to protected endpoints
    Affected if Users can access resources or pages outside their authorized permissions by modifying user-supplied input values

The environment is affected if the installed MyRezzta version is s2.02.02 or higher but earlier than v2.05.01, and the application uses user-controlled keys in its authorization logic without proper server-side permission validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper server-side authorization checks that validate user permissions before granting access to resources, ensuring user-controlled keys cannot be exploited to bypass access controls.

Recommended fix Moderate confidence

v2.05.01

  1. 1. Identify the current installed version of Akinsoft MyRezzta (confirmed affected versions are s2.02.02 through versions before v2.05.01)
  2. 2. Back up all MyRezzta databases and configuration files before upgrading
  3. 3. Obtain the v2.05.01 release of Akinsoft MyRezzta from the official vendor
  4. 4. Install v2.05.01 following the vendor's standard upgrade procedure
  5. 5. Verify the installation completed successfully
  6. 6. Test that the authorization bypass vulnerability is remediated by confirming users cannot access unauthorized resources through direct object reference manipulation
  7. 7. Verify normal application functionality remains intact

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13063 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-13063 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data