# CVE-2020-10248: Information disclosure in n/a

> Remote attackers can discover passwords by accessing a specific PHP script, potentially leading to unauthorized access on BWA DiREX-Pro devices.

- **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:** 9 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7wr3-h277-5p7q

## What is CVE-2020-10248?

CVE-2020-10248 is a high-severity vulnerability in n/a, published on 9 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

BWA DiREX-Pro 1.2181 devices allow remote attackers to discover passwords via a direct request to val_users.php3.

Weakness: CWE-425 (Direct Request)

## Which versions are affected by CVE-2020-10248?

It affects 1 product.


Products: Meinbwa Direx-Pro Firmware.

## How do I fix CVE-2020-10248?

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

## Is CVE-2020-10248 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-10250](https://insights.sbomify.com/CVE-2020-10250/): Command injection in n/a (critical 9.8)
- [CVE-2020-10249](https://insights.sbomify.com/CVE-2020-10249/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-10248 and fix it if it is affected.

What it is: CVE-2020-10248 is a high-severity vulnerability in n/a, published on 9 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-10248 in the wild and no public exploit code.

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-2020-10248/ (Markdown: https://insights.sbomify.com/CVE-2020-10248/index.md)
```

## Sources

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

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