LiveActive security incident?Get immediate response
CVE Record

CVE-2025-15610: The .NET Remoting framework used by OpenText Fax (RightFax) includes known security vulnerabilities that co...

The .NET Remoting framework used by OpenText Fax (RightFax) includes known security vulnerabilities that could be exploited if the service is exposed in environments where the remoting ports are accessible.

CriticalCVSS 9.3Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

OpenText RightFax uses .NET Remoting in a way that includes known security weaknesses. If the remoting service is reachable over the network, an unauthenticated attacker may be able to compromise confidentiality, integrity, and availability. This is critical for organizations that expose RightFax services beyond tightly controlled internal networks.

Executive priority

Treat as urgent if RightFax is business-critical or reachable from broad networks. Prioritize exposure reduction immediately, then follow OpenText guidance for remediation. Lack of confirmed exploitation lowers certainty, not severity.

Technical view

CVE-2025-15610 affects OpenText RightFax versions 16.6, 20.2, 21.2, 22.2, 23.4, 24.4, and 25.4. The CVE maps to CWE-502 and describes risk from .NET Remoting when remoting ports are accessible. CVSS 4.0 is 9.3 with network attack vector, low complexity, no privileges, and no user interaction.

Likely exposure

Exposure is most likely where RightFax .NET Remoting ports are reachable from untrusted networks, broad internal networks, VPN users, or partner connections. Systems isolated behind strict firewall rules are materially less exposed, but still need vendor review.

Exploitation context

The provided sources do not state active exploitation, and this CVE is not marked as CISA KEV in the supplied data. The risk remains high because the issue is unauthenticated, network-reachable, and tied to unsafe deserialization class weakness.

Researcher notes

Public detail is limited. The CVE identifies .NET Remoting exposure and CWE-502 but does not provide port numbers, vulnerable components, or patch identifiers in the supplied bundle. Avoid assumptions; validate against OpenText KB0861863 and local RightFax architecture.

Mitigation direction

  • Review OpenText KB0861863 and apply any vendor-prescribed update or configuration change.
  • Restrict RightFax remoting ports to only required trusted systems.
  • Block internet and broad internal access to remoting services.
  • Segment RightFax servers from general user and partner networks.
  • Monitor OpenText advisories for updated remediation details.

Validation and detection

  • Inventory RightFax servers and confirm affected version presence.
  • Identify whether .NET Remoting services are enabled.
  • Verify remoting ports are not reachable from untrusted networks.
  • Review firewall rules, VPN access, and partner connectivity paths.
  • Check OpenText guidance for version-specific validation steps.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-15610 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.3 (4.0)
Known Exploited
No
Published

Vector: 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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.3CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NPrimary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

9.3Critical
CVSS 4.0 vector shape for CVE-2025-15610Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
OpenText, IncRightFax16.6, 20.2, 21.2, 22.2, 23.4, 24.4, 25.4unknown
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.