CVE-2025-20628 — Insufficient granularity of access control for Remote Connector Servers in client mode

An insufficient granularity of access control vulnerability exists in PingIDM (formerly ForgeRock Identity Management) where administrators cannot properly configure access rules for Remote Connector Servers (RCS) running in client mode. This means attackers can spoof a client-mode RCS (if one exists) to intercept and/or modify an identity’s security-relevant properties, such as passwords and account recovery information. This issue is exploitable only when an RCS is configured to run in client mode.

Published Apr 7, 2026Updated Apr 8, 2026Sources: cvelistV5, Ping Identity

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

chance of exploitation in 30 days

Affects

ping identity

pingidm

CVSS base

6.9

MEDIUM

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

can an attacker script all four kill-chain steps

Technical impact

Total

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)

ping identity

Products (1)

pingidm

Every base score collected

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

Score	Version	Severity	Expl.	Impact	Source
6.9	CVSS 4.0	MEDIUM	—	—	cvelistV5

Weakness & attack patterns

CWE-1220

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

T1574.010Hijack Execution Flow: ServicesFile Permissions Weakness

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Search application, proxy, and WAF logs for requests touching /or.

References

2 on the record

Elsewhere on this site

ping identityevery CVE for this vendor
CWE-1220other 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.