CVE-2023-40148· NVD / CVE Program· CNA Ping Identity

PingFederate Server Side Request Forgery vulnerability

Noroxi assessment

Priority: Monitor (action score 26/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.46% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Server-side request forgery (SSRF) in PingFederate allows unauthenticated http requests to attack network resources and consume server-side resources via forged HTTP POST requests.

MediumCVSS 6.5 · v3.1—No exploit No fix recorded

Published: Apr 9, 2024
Updated: Jun 17, 2026
EPSS: 0.4% · 38th percentile
CWE: CWE-918

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 26 / 40 · 6.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · Ping Identity: 6.5; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
pingidentity	pingfederate	cpe:2.3:a:pingidentity:pingfederate

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Ping Identity). Independent of NVD's CPE analysis and usually ahead of it.

Ping Identity PingFederate
- 11.3.0 and later · up to and including 11.3.2affected
- 11.2.0 and later · up to and including 11.2.7affected
- 11.1.0 and later · up to and including 11.1.8affected
- 11.0.0 and later · up to and including 11.0.8affected

Same product

ping identity: all records

Other highest-scoring records for the same primary product.

CVE-2026-20773Improper Authorization in PingFederate Administrative Expression Evaluation Endpoint
34Monitor
CVE-2024-25573Stored Cross-Site Scripting in Administrative Console Context
27Monitor
CVE-2025-22854Possible thread exhaustion from processing http responses in PingFederate Google Adapter
27Monitor

Published before and after this one in the same product

Later →CVE-2024-21832Jul 9, 2024 · PingFederate REST API Data Store Injection
14Monitor
Later →CVE-2025-21085Jun 15, 2025 · PingFederate OAuth Grant attribute duplication may use excessive memory
8Monitor
Later →CVE-2025-26862Oct 27, 2025 · PingFederate unexpected browser flow initiation in redirectless mode
0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope