Is this vulnerability remotely exploitable?

Yes. Any attacker who can obtain or control a patient portal account and submit payment information can remotely plant a stored XSS payload that later executes in a staff member's browser when they review the payment.

What level of access does an attacker need to exploit this?

The attacker needs the ability to log into the patient portal and submit payment-related data, or otherwise control such an account (for example, via account compromise or social engineering). Direct access to staff credentials is not required.

What is the safest general fix pattern for this issue?

The most robust fix is to ensure that every user-controlled value rendered in staff-facing views is passed through context-aware output encoding or escaping routines, ideally via a templating system that auto-escapes by default, and to normalize/validate payment fields to simple text formats.

Severity:

HIGH RISK

(8.7)

Stored Cross-Site Scripting (CWE-79) in OpenEMR Patient Portal Payment Flow

CVE-2026-33346

Published:

Mar 19, 2026

Status:

Modified

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

Stored Cross-Site Scripting (XSS)

CWE:

CWE-79

Impact:

Client-Side Code Execution in Staff Browsers

Severity:

HIGH RISK

(8.7)

CVSS Version:

3.1

Vulnerability Type

Category:

Stored Cross-Site Scripting (XSS)

CWE:

CWE-79

Impact:

Client-Side Code Execution in Staff Browsers

Severity:

HIGH RISK

(8.7)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Stored Cross-Site Scripting (CWE-79) in OpenEMR Patient Portal Payment Flow

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal