# CVE-2025-1886: Pass-Back vulnerability in Sage 200 Spain

> An authenticated administrator can discover stored SMTP credentials in Sage 200 Spain, exposing sensitive configuration data.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Mar 2025
- **Updated:** 7 Mar 2025
- **Also known as:** GHSA-5hrm-fvfm-h7c3

## What is CVE-2025-1886?

CVE-2025-1886 is a high-severity vulnerability in Sage 200 Spain, published on 7 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Pass-Back vulnerability in versions prior to 2025.35.000 of Sage 200 Spain. This vulnerability allows an authenticated attacker with administrator privileges to discover stored SMTP credentials.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2025-1886 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1886 is a high-severity vulnerability in Sage 200 Spain, published on 7 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1886 in the wild and no public exploit code.

Affected product: Sage 200 Spain. 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-1886/ (Markdown: https://insights.sbomify.com/CVE-2025-1886/index.md)
```

## Sources

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

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