LiveActive security incident?Get immediate response
CVE Record

CVE-2019-10219: A vulnerability was found in Hibernate-Validator.

A vulnerability was found in Hibernate-Validator. The SafeHtml validator annotation fails to properly sanitize payloads consisting of potentially malicious code in HTML comments and instructions. This vulnerability can result in an XSS attack.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2019-10219 is an XSS weakness in Hibernate Validator’s SafeHtml annotation. It may allow malicious script-like content hidden in HTML comments or processing instructions to survive validation and later execute when rendered by an application.

Executive priority

Schedule remediation in the normal vulnerability queue, faster for internet-facing applications that render user-supplied HTML. Business impact is mainly account, session, or data exposure through XSS rather than infrastructure takeover.

Technical view

SafeHtml did not properly sanitize potentially malicious HTML comments and instructions, mapping to CWE-79. The CVSS 3.0 score is 6.5 with network attack vector, low complexity, no privileges, and no user interaction listed in the bundle.

Likely exposure

Exposure is most likely in Java applications using affected Hibernate Validator versions and relying on SafeHtml to sanitize user-controlled HTML before display. Downstream products may inherit risk through bundled dependencies or vendor packages.

Exploitation context

The bundle references public proof-of-concept repositories, but KEV is false and no cited source confirms active exploitation. Treat this as a known, reproducible XSS issue rather than a confirmed in-the-wild campaign.

Researcher notes

Evidence supports a SafeHtml sanitization bypass involving HTML comments and instructions. Source detail is limited on exact fixed release ranges; use upstream commits and vendor advisories to confirm remediation state for each dependency path.

Mitigation direction

  • Identify all applications and packages using Hibernate Validator SafeHtml.
  • Upgrade Hibernate Validator per upstream or vendor guidance; Apache Pluto referenced 6.0.20.Final.
  • Apply relevant Red Hat, Oracle, NetApp, or other downstream vendor updates where applicable.
  • Review uses of SafeHtml and avoid treating validation as complete output encoding.
  • Check vendor advisories for exact fixed versions in packaged products.

Validation and detection

  • Search SBOMs and dependency manifests for hibernate-validator versions listed as affected.
  • Find code paths using the SafeHtml annotation on user-controlled fields.
  • Confirm rendered HTML output is encoded or sanitized by a maintained sanitizer.
  • Verify deployed packages include vendor fixes or upstream patched commits.
  • Prioritize internet-facing forms, admin portals, comments, profiles, and rich-text inputs.
Prepared
Confidence
medium
Sources
11

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-10219 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
20Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.0MediumCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N3.92.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

6.5Medium
CVSS 3.0 vector shape for CVE-2019-10219Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Hibernatehibernate-validator6.0.0.Alpha1, 6.1.0.Alpha1, 6.0.18.Final, 6.1.0.Finalunknown
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.