# CVE-2025-40671: SQL injection vulnerability in AES Multimedia's Gestnet

> An attacker can manipulate the fk_remoto_central parameter to read, create, update, or delete database records in Gestnet.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA: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 May 2025
- **Updated:** 4 Jun 2025
- **Also known as:** GHSA-875j-77w8-r9fv

## What is CVE-2025-40671?

CVE-2025-40671 is a critical SQL injection vulnerability in AES Multimedia Gestnet, published on 26 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection vulnerability in AES Multimedia's Gestnet v1.07. This vulnerability allows an attacker to retrieve, create, update and delete databases via the ‘fk_remoto_central’ parameter on the ‘/webservices/articles.php’ endpoint.

Weakness: CWE-93 (Improper Neutralization of CRLF Sequences)

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


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

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

## Is CVE-2025-40671 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-40671 is a critical SQL injection vulnerability in AES Multimedia Gestnet, published on 26 May 2025. 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-2025-40671 in the wild and no public exploit code.

Affected product: AES Multimedia Gestnet. 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-40671/ (Markdown: https://insights.sbomify.com/CVE-2025-40671/index.md)
```

## Sources

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

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