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

CVE-2025-12008

HIGH · 8.8 CVSS v3.1 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 APPYAP Technology and Information Inc. Yaay Social Media App allows Accessing Functionality Not Properly Constrained by ACLs. This issue affects Yaay Social Media App: from 3.8.0 through 24102025.

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

The Yaay Social Media App versions 3.8.0 through 24102025 contains an authorization bypass vulnerability where the application fails to properly constrain access to certain functionality based on Access Control Lists (ACLs). Attackers can exploit user-controlled keys to access features and data outside their intended permissions scope, effectively bypassing ACL enforcement.

MitigationImplement proper authorization validation on all sensitive endpoints, enforce server-side ACL checks, and ensure user permissions are validated before granting access to any functionality or data.

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 sensitive operations in your application
    Review your application documentation or codebase to map out functions, endpoints, or APIs that should be restricted by Access Control Lists (ACLs). Common examples include: admin panels, data export features, user management, file access, or financial transactions.
    Affected if Your application has functionality that should be ACL-protected but you cannot confirm ACL enforcement.
  2. Locate user-controlled parameters used for access decisions
    Search your application code for places where request parameters, headers, cookies, or URL segments are used to determine which resources or functions a user can access. Look for patterns like: userId, role, permission, resourceId, or any parameter that influences access control logic.
    Affected if User-supplied input directly determines access to sensitive operations without validation against an ACL.
  3. Verify ACL validation occurs before operation execution
    Trace the code path from the sensitive endpoint/function to confirm that permission checks happen BEFORE the operation executes. Review the authorization logic to ensure it queries an ACL or permission store before allowing the action.
    Affected if Sensitive operations execute without first validating user permissions against an ACL, or the ACL check can be bypassed.
  4. Test parameter manipulation for unauthorized access
    If you have access to the application, attempt to modify user-controlled parameters (such as IDs, roles, or keys) in requests to access resources or functions outside your assigned permissions. Compare the expected behavior against actual results.
    Affected if Modifying a user-controlled parameter allows access to functionality that should be restricted by your assigned permissions.
  5. Inspect server-side validation of access parameters
    Review server-side code to confirm that all parameters used for access decisions are validated server-side, not just client-side. Ensure the server independently verifies permissions rather than trusting client-supplied permission data.
    Affected if The server accepts access decisions based on user-controlled parameters without independent validation, allowing ACL bypass.

You are affected if your application uses user-controlled parameters to determine access to sensitive operations without properly validating permissions against an ACL server-side before executing the action.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization validation on all sensitive endpoints, enforce server-side ACL checks, and ensure user permissions are validated before granting access to any functionality or data.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12008 — 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-2025-12008 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