# CVE-2025-12008: IDOR in APPYAP's Yaay Social Media App

> Attackers can bypass authorization controls to access or modify other users' data in the Yaay Social Media App.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 May 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-j2gg-fc46-32rv

## What is CVE-2025-12008?

CVE-2025-12008 is a high-severity missing authorization vulnerability in APPYAP Technology and Information Inc. Yaay Social Media App, published on 14 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2025-12008?


## How do I fix CVE-2025-12008?

No fix has been published for CVE-2025-12008 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-12008 being exploited?

There is no known exploitation of CVE-2025-12008 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-12008 and fix it if it is affected.

What it is: CVE-2025-12008 is a high-severity missing authorization vulnerability in APPYAP Technology and Information Inc. Yaay Social Media App, published on 14 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-12008 in the wild and no public exploit code.

Affected product: APPYAP Technology and Information Inc. Yaay Social Media App. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-12008/ (Markdown: https://insights.sbomify.com/CVE-2025-12008/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-12008
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-12008
- OSV: https://osv.dev/vulnerability/CVE-2025-12008

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-12008/
Summaries are generated and may contain mistakes; the official description above is the record.