Medium Cross-site scripting

CVE-2026-12047 — pgAdmin 4: HTML injection in cloud verify_credentials / deploy endpoints via unsanitised SDK exception text

HTML injection in pgAdmin 4's cloud deployment module. The verify_credentials, deploy, regions, and update-server endpoints under /rds/, /azure/, /google/, and the top-level /cloud/ blueprint propagated AWS / Azure / Google SDK exception text — and the related file-resolution and database-commit exception text — into the JSON response body (the info and errormsg fields) without HTML-encoding. The Cloud Wizard frontend rendered these strings through html-react-parser, so an attacker-influenced exception message embedded structural HTML directly into the wizard's DOM. The reported entry point is /rds/verify_credentials/. An authenticated pgAdmin user submits a crafted access_key whose value contains an <iframe/src=...> payload; AWS STS rejects the credential with an IncompleteSignature exception whose text quotes the access_key verbatim; the pgAdmin backend forwards that text into the JSON info field; the Cloud Wizard's FormFooterMessage parses it as HTML. The browser fetches the iframe's src from an attacker-controlled host, and JavaScript executing inside the cross-origin iframe writes to parent.location, redirecting the victim's pgAdmin tab. Because the injection renders inside pgAdmin's own interface, X-Frame-Options and Content-Security-Policy frame-ancestors do not mitigate it. Baseline impact is self-targeted (the same user who supplied the payload sees the injection); escalation against other authenticated users requires an additional cross-site request-forgery primitive capable of submitting the malformed credential request with a valid X-pgA-CSRFToken in the victim's browser context. The same unsanitised-error-into-JSON pattern was present across multiple sibling endpoints — Azure's check_cluster_name_availability, every Google endpoint that surfaces SDK errors (verification_ack, projects, regions, instance_types, database_versions, the verify_credentials path-resolution branches), the central /deploy endpoint that bubbles str(e) from deploy_on_rds / deploy_on_azure / deploy_on_google, and update_cloud_server which surfaces the str(e) from a failing db.session.commit — all of which are now covered. Fix HTML-escapes every external/SDK exception string at the endpoint sink via a new shared sanitize_external_text helper (HTML escape with control-character strip), promoted out of the psycopg3 driver into web/pgadmin/utils/text_sanitize.py. The Cloud Wizard frontend additionally renders its FormFooterMessage in plain-text mode for backend-derived strings, so the value is never parsed as HTML even if a future sink forgets the escape. This issue affects pgAdmin 4: from 6.6 before 9.16.

Published Jun 18, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: PostgreSQL

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+2
Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

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

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.22%

ahead of 12% of scored CVEs · Oct 15, 2026

Affects

Pgadmin

Pgadmin 4 and 1 more

CVSS base

5.4

Medium · 3 source(s)

CISA SSVC assessment CISA

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

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

Documented patch — github.com (NIST National Vulnerability Database)
Documented patch — github.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Pgadmin Pgadmin 4, Pgadmin.org pgAdmin 4).
Apply the fixed version or the patch documented under Remediation.
Exploitation requires user interaction: tighten email/web filtering and warn affected users.
Search available logs for exploit probes matching the vulnerability class (cross-site scripting), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Pgadmin	Pgadmin 4	≥ 6.6 and < 9.16	Vulnerable	NIST National Vulnerability Database
Pgadmin.org	pgAdmin 4	≥ 6.6 and < 9.16	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

Low

User interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Every base score collected

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

Score	Version	Severity	Expl.	Impact	Scored by
4.8	CVSS 4.0	Medium	—	—	f86ef6dc-4d3a-42ad-8f28-e6d5547a5007 via NIST National Vulnerability Database
4.8	CVSS 4.0	Medium	—	—	PostgreSQL via CVE Program (cve.org) e CISA ADP
5.4	CVSS 3.1	Medium	2.3	2.7	nvd@nist.gov via NIST National Vulnerability Database
3.5	CVSS 3.1	Low	2.1	1.4	f86ef6dc-4d3a-42ad-8f28-e6d5547a5007 via NIST National Vulnerability Database
3.5	CVSS 3.1	Low	—	—	PostgreSQL via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N (score shown at the top: nvd@nist.gov)

Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 5.4 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-79 · Cross-site Scripting (XSS)

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 0.22%

Detection

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

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Monitor CSP violation reports and script payloads in reflected parameters.

web/proxy/WAF logsnetwork IDS/IPSapplication logs

Timeline

What happened to this CVE, newest first.

2026
Affected products added · pgadmin.org/pgadmin 4
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
Fix documented
Oct 13, 2026 · NIST National Vulnerability Database
CVSS changed · 5.4
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Jun 18, 2026 · PostgreSQL

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

2 on the record

github.com/pgadmin-org/pgadmin4/issues/10069
Issue Tracking, Patch, issue-tracking, NIST National Vulnerability Database
github.com/pgadmin-org/pgadmin4/commit/60d149864b5fdd99675754c7996637737a24fce3
Patch, patch, NIST National Vulnerability Database

Elsewhere on this site

Pgadmin
every CVE for this vendor

Cross-site scripting
same class

CWE-79
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-86864 pgAdmin 4: Argument and connection-string injection via the database field in the Backup tool 29d
Medium CVE-2026-86861 pgAdmin 4: File Manager save_file writes through a symbolic link planted after the containment check 29d
Medium CVE-2026-86862 pgAdmin 4: Connection-string injection via the database field in the Restore and Maintenance tools 29d
Critical CVE-2026-86863 pgAdmin 4: Authentication bypass via a client-controlled identity header in Webserver authentication mode 29d
Critical CVE-2026-17566 pgAdmin 4: RCE via backslash-escape mismatch in Import/Export Data query guard (incomplete defense, sibling gap to CVE-2025-13780) Jul 31, 2026
Medium CVE-2026-17348 pgAdmin 4: Missing authentication decorator on Constraints, preferences, Debugger and Schema Diff routes allows unauthenticated access in SERVER mode (incomplete fix for CVE-2026-12046) Jul 31, 2026

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.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-12047 is "pgAdmin 4: HTML injection in cloud verify_credentials / deploy endpoints via unsanitised SDK exception text", rated Medium. It affects Pgadmin 4 (Pgadmin); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.4 describes technical severity. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.