CVE Intelligence
Skip to main content
HIGH

CVE-2025-1886

CVE-2025-1886 — Pass-Back vulnerability in Sage 200 Spain

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.

Published Updated Sources: cvelistV5, INCIBE

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

chance of exploitation in 30 days

Affects

sage

sage_200_spain

CVSS base

7.1

HIGH

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

sage

Products (1)

sage 200 spain

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
7.1CVSS 4.0HIGH——cvelistV5

Weakness & attack patterns

  • CWE-522

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1552.004Unsecured Credentials: Private Keys
  • T1558.003Steal or Forge Kerberos Tickets: Kerberoasting
  • T1543Create or Modify System Process

References

1 on the record

Elsewhere on this site

  • sageevery CVE for this vendor
  • CWE-522other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.