# CVE-2025-61121: Information disclosure in n/a

> Attackers can obtain cloud service credentials from the Mobile Scanner Android App, leading to sensitive information disclosure and abuse of cloud resources.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Oct 2025
- **Updated:** 30 Oct 2025
- **Also known as:** GHSA-37qf-jwxf-87wg

## What is CVE-2025-61121?

CVE-2025-61121 is a high-severity vulnerability in n/a, published on 30 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Mobile Scanner Android App version 2.12.38 (package name com.glority.everlens), developed by Glority Global Group Ltd., contains a credential leakage vulnerability. Improper handling of cloud service credentials may allow attackers to obtain them and carry out unauthorized actions, such as sensitive information disclosure and abuse of cloud resources. Successful exploitation could result in privacy breaches and misuse of the platform infrastructure.

Weakness: CWE-523 (Unprotected Transport of Credentials)

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


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

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

## Is CVE-2025-61121 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61121 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-61121 is a high-severity vulnerability in n/a, published on 30 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61121 exists.

Affected product: n/a. 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-61121/ (Markdown: https://insights.sbomify.com/CVE-2025-61121/index.md)
```

## Sources

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

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