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

> Unauthenticated attackers can access plaintext usernames and passwords from the users.json file in GroceryMart.

- **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:** 26 Nov 2025
- **Updated:** 28 Nov 2025
- **Also known as:** GHSA-rmf9-x9hc-v3pr

## What is CVE-2025-65278?

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

### Official description

An issue was discovered in file users.json in GroceryMart commit 21934e6 (2020-10-23) allowing unauthenticated attackers to gain sensitive information including plaintext usernames and passwords.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Komal97 Grocerymart.

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

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

## Is CVE-2025-65278 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65278 is a high-severity vulnerability in n/a, published on 26 Nov 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-65278 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-65278/ (Markdown: https://insights.sbomify.com/CVE-2025-65278/index.md)
```

## Sources

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

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