vciy

CVE-2025-1735

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

pgsql extension does not check for errors during escaping

CVE-2025-17354 of 4 sources documented this
24

rank 24 = 0 + 19 + 0 + 5 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00983  ·  without this subject the record ranks 24

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.5, from NVD  ·  without this subject the record ranks 5

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 24

How much of the world it touches

NVD CPE configurations

4 products in the CPE ranges  ·  without this subject the record ranks 19

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 24

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$30,000over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$30,000 = $4.99M incident cost x 0.6121449559255632 exposure x 0.00983 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.00983EPSSNOT IN KEVas of 2026-09-20
Severity5.9 MEDIUMreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2025-07-14, 427 days at 0.01, as of 2026-09-14. arc-rules@v1

Foresight · where to check next

WordPressCVE-2023-34362CVE-2021-42258CVE-2020-29574CVE-2017-18362Fortinet1735

This record is one instance of CWE-89, improper neutralization of special elements used in an sql command ('sql injection'). The index holds 20889 prior instances of this class, 31 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

Sources disagree here.

Severity score
Php5.9 MEDIUMreceipt
NVD7.5 HIGHreceipt

Both shown, dated. We don't pick winners. disagreement-rules@v1

Running PHP? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · no user interaction · high attack complexityreceipt
ImpactComplete availability lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'); CWE-476 NULL Pointer Dereferencereceipt
Published consequencesCWE-89: Confidentiality, Integrity, Availability: Execute Unauthorized Code or Commands; Confidentiality: Read Application Data; Authentication: Gain Privileges or Assume Identity, Bypass Protection…[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in8.1.33; 8.2.29; 8.3.23; 8.4.10receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA5.9 MEDIUMreceipt
CVSS, NVD7.5 HIGHreceipt
Exploit probability0.00983 · top 39% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byphpreceipt
Recorded changes39 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productPHP Group PHPreceipt
Published rangesphp >= 8.1.0 < 8.1.33; php >= 8.2.0 < 8.2.29; php >= 8.3.0 < 8.3.23; php >= 8.4.0 < 8.4.10receipt
Fixed in8.1.33; 8.2.29; 8.3.23; 8.4.10receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

Attack path

Unauthenticated network requestno credentials, no interactionPHPCWE-89 SQL injectionAvailability lossA:Hexploits CWE-89data compromise

What it is stated by the CNA

In PHP versions:8.1.* before 8.1.33, 8.2.* before 8.2.29, 8.3.* before 8.3.23, 8.4.* pgsql and pdo_pgsql escaping functions do not check if the underlying quoting functions returned errors. This could cause crashes if Postgres server rejects the string as invalid. receipt

NVD's analysis a second authority

severity
7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
weakness
CWE-89; CWE-476
affected versions
php >= 8.1.0 < 8.1.33; php >= 8.2.0 < 8.2.29; php >= 8.3.0 < 8.3.23; and 1 more, listed in full below
also scored by
[email protected] 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

The CNA scored it 5.9 and NVD 7.5. Both are shown because both were published; we do not pick one.

check it yourself github.com receipt

Movement the material steps

14 Jul 20250.00052
15 Jun 20260.00953 · scoring model v2026.06.15
14 Sep 20260.00983
Show all 39 observations
14 Jul 20250.00052
16 Jul 20250.0007
19 Jul 20250.00068
23 Jul 20250.00071
14 Aug 20250.00077
16 Aug 20250.00115
25 Aug 20250.00096
19 Sep 20250.001
1 Oct 20250.00163
27 Oct 20250.001
28 Oct 20250.00163
4 Nov 20250.0014
5 Nov 20250.00132
12 Nov 20250.00171
18 Nov 20250.00137
21 Nov 20250.00171
28 Nov 20250.00061
10 Dec 20250.00059
20 Dec 20250.00064
21 Dec 20250.00076
22 Dec 20250.0007
27 Dec 20250.0005
28 Dec 20250.0007
29 Jan 20260.00076
1 Feb 20260.0007
6 Feb 20260.00093
16 Feb 20260.00089
18 Feb 20260.00096
19 Feb 20260.00089
6 Mar 20260.00096
9 Mar 20260.00089
18 Mar 20260.00098
29 Mar 20260.00134
8 Apr 20260.0015
29 Apr 20260.00162
9 May 20260.00589
15 Jun 20260.00953
11 Aug 20260.01
14 Sep 20260.00983

39 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00983Published2025-07-13Index as of2026-09-14

The record had been public for 1 year, 2 months when this index was last written.

Published 2025-07-13 receipt · Index as of 2026-09-14 derived

The pattern, elsewhere

This record is one instance of CWE-89, improper neutralization of special elements used in an sql command ('sql injection'). The index holds 20889 prior instances of this class, 31 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2026-60137 · WordPressmatches 6 of 10KEV listed · 2026receipt
CVE-2023-34362matches 5 of 9KEV listed · 2023receipt
CVE-2021-42258matches 5 of 9KEV listed · 2021receipt
CVE-2020-29574matches 5 of 9KEV listed · 2020receipt
CVE-2017-18362matches 5 of 9KEV listed · 2019receipt
CVE-2023-48788 · Fortinet FortiClientEMSmatches 5 of 10KEV listed · 2024receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

20889 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Its defect family

php group php

Of the 3 records in this family, this is the only one holding a stated fix version: 8.1.33; 8.2.29; 8.3.23; 8.4.10.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2025-1735.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.