# CVE-2018-25177: Data Center Audit 2.6.2 Cross-Site Request Forgery via dca_resetpw.php

> Attackers can reset administrator passwords via CSRF, gaining administrative access to Data Center Audit.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Mar 2026
- **Updated:** 9 Mar 2026
- **Also known as:** GHSA-m59j-fmv4-9rmv

## What is CVE-2018-25177?

CVE-2018-25177 is a medium-severity vulnerability in Sourceforge Data Center Audit, published on 6 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Data Center Audit 2.6.2 contains a cross-site request forgery vulnerability that allows attackers to reset administrator passwords without authentication by submitting crafted POST requests. Attackers can send requests to dca_resetpw.php with parameters updateuser, pass, pass2, and submit_reset to change the admin account password and gain administrative access.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2018-25177 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25177 is a medium-severity vulnerability in Sourceforge Data Center Audit, published on 6 Mar 2026. 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-2018-25177 exists.

Affected product: Sourceforge Data Center Audit. 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-25177/ (Markdown: https://insights.sbomify.com/CVE-2018-25177/index.md)
```

## Sources

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

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