CVE-2025-1886
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPass-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a Pass-Back vulnerability in Sage 200 Spain that allows an authenticated administrator to discover stored SMTP credentials. The vulnerability exists in versions prior to 2025.35.000, where the application does not properly protect SMTP credential storage, enabling a privileged user to retrieve these credentials through the pass-back mechanism.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- Authentication
- X
- User interaction
- None
- Scope
- X
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Sage 200 Spain installationIdentify Sage 200 Spain in your environment and verify it is deployedAffected if Sage 200 Spain is installed
-
Check the installed versionAccess the application version information (typically in Help > About or the main application interface)Affected if Version is earlier than 2025.35.000
-
Determine if SMTP is configuredNavigate to the email settings or SMTP configuration section in the application to see if SMTP credentials are storedAffected if SMTP credentials are configured and stored in the application
-
Verify administrator accessConfirm that an authenticated administrator account exists in the Sage 200 Spain environmentAffected if At least one administrator user account is present
You are affected if Sage 200 Spain version is earlier than 2025.35.000, SMTP credentials are configured, and an administrator user has access to retrieve them through the pass-back mechanism.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Sage 200 Spain to version 2025.35.000 or later. After upgrading, audit SMTP configuration and consider rotating SMTP credentials as a precautionary measure.
Sage 200 Spain version 2025.35.000
- 1. Identify the current installed version of Sage 200 Spain
- 2. Upgrade Sage 200 Spain to version 2025.35.000 or later to remediate the vulnerability
- 3. After upgrading, verify that SMTP credentials are properly protected and accessible only through authorized mechanisms
- 4. Review administrator access logs to confirm no unauthorized credential access occurred prior to the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1886 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-1886 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data