# CVE-2018-25130: Beward Intercom 2.3.1 Local Credentials Disclosure via Unencrypted Database

> Local attackers can read unencrypted database files to extract plain-text credentials, enabling unauthorized access to IP cameras and door stations.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Dec 2025
- **Updated:** 24 Dec 2025
- **Also known as:** GHSA-hjwr-h73m-h7pf

## What is CVE-2018-25130?

CVE-2018-25130 is a medium-severity vulnerability in BEWARD Intercom, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Beward Intercom 2.3.1 contains a credentials disclosure vulnerability that allows local attackers to access plain-text authentication credentials stored in an unencrypted database file. Attackers can read the BEWARD.INTERCOM.FDB file to extract usernames and passwords, enabling unauthorized access to IP cameras and door stations.

Weakness: CWE-256 (Plaintext Storage of a Password)

## Which versions are affected by CVE-2018-25130?


## How do I fix CVE-2018-25130?

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

## Is CVE-2018-25130 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25130 and fix it if it is affected.

What it is: CVE-2018-25130 is a medium-severity vulnerability in BEWARD Intercom, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25130 exists.

Affected product: BEWARD Intercom. 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-2018-25130/ (Markdown: https://insights.sbomify.com/CVE-2018-25130/index.md)
```

## Sources

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

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