CVE-2026-0949VulnerabilityPublished 16 Jan 2026

CVE-2026-0949: EnterpriseDB Postgres Enterprise Manager (PEM) · Cross-site Scripting

Affects EnterpriseDB Postgres Enterprise Manager (PEM)Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
EnterpriseDBPostgres Enterprise Manager (PEM)	Affected >=9 <9.8.1	Fixed in–

AI-suggested

European organizations should immediately upgrade PEM to version 9.8.1 or later, where the vulnerability is patched. Until patching is possible, restrict access to the Manage Charts menu strictly to trusted administrators and monitor for unusual activity. Implement strict role-based access controls (RBAC) to minimize the number of users with pem_admin or pem_super_admin privileges. Conduct regular audits of user privileges and review chart configurations for suspicious or unauthorized scripts. Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in the PEM web interface. Additionally, educate administrators about the risks of injecting untrusted input and encourage safe handling of chart creation. Network segmentation and monitoring of PEM traffic can help detect exploitation attempts. Finally, maintain up-to-date backups and incident response plans to quickly recover from potential compromises.

Description

PEM versions prior to 9.8.1 are affected by a stored Cross-site Scripting (XSS) vulnerability that allows users with access to the Manage Charts menu to inject arbitrary JavaScript when creating a new chart, which is then executed by any user accessing the chart. By default only the superuser and users with pem_admin or pem_super_admin privileges are able to access the Manage Charts menu.

Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality and integrity of data managed through PEM. Attackers with administrative access could inject malicious scripts that compromise session tokens, steal sensitive information, or perform unauthorized actions within the PEM interface. This could lead to unauthorized access to database management functions or leakage of sensitive operational data. Since PEM is used for managing PostgreSQL databases, which are widely deployed in enterprise environments, exploitation could affect critical infrastructure and business operations. The requirement for high privileges to exploit reduces the likelihood of external attackers directly leveraging this vulnerability, but insider threats or compromised administrative accounts could be leveraged. The stored XSS nature means that even non-privileged users who view the charts could be impacted, potentially leading to broader compromise. Disruption of database management activities could also indirectly affect availability of services dependent on these databases.

References

enterprisedb.com/docs/security/advisories/cve20260949/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Jan 2026, 17:06 UTC

Technical details

References

Community reviews

Related threats