CM HIPAA Forms < 3.3.2 - hipaa_forms+ Privilege Escalation via cm_hipaa_update_user_role
CVSS score
—
EPSS probability
—
Risk score
—
Published
4 h ago
Resmî kaynaklarda yeterli kanıt bulunamadı. Bu sonuç “yama yok” anlamına gelmez.
Impact on My Inventory
Only the personal products you have added to your account are assessed; an organisation's inventory does not appear here.
Checking session…
Vulnerability description
DayBreach AI Explanation
Verified against sourcesSources read
2
Source agreement
Tam uyum
Evidence confidence
%63
Short explanation
Versions of the HIPAA Forms WordPress plugin prior to 3.3.2 do not perform a capability check when rebuilding its custom user role, allowing a user who already holds that role to grant administrator capabilities and achieve privilege escalation (S0,S1,S2). No active exploitation is listed in the CISA KEV program and the patch status could not be verified in official sources (S0).
An attacker who gains administrator privileges can fully control the site and expose sensitive data.
What should be done?
- Upgrade to version 3.3.2 or later when available
- Monitor vendor advisory for fixes
- Regularly audit user roles and capabilities
- Log suspicious role modifications
- Apply the principle of least privilege
Chain of evidence and sources
HIPAA Forms eklentisinin 3.3.2 öncesi sürümlerinde, rol yeniden oluşturma sırasında yetenek kontrolü eksikliği, mevcut rolü taşıyan bir kullanıcının yönetici yetkileri eklemesine izin verir.
CISA KEV listesinde bu CVE için aktif istismar kaydı bulunmamaktadır.
Resmî kaynaklarda yama durumu doğrulanamadığı için, mevcut bir düzeltme sürümü kesin olarak belirlenememiştir.
Show the technical text from the sources
The HIPAA Forms WordPress plugin before 3.3.2 does not perform a capability check when handling a request that rebuilds its own custom user role, allowing a user who already holds that role to grant it administrator-level capabilities and escalate their privileges.
This explanation was compiled automatically from the source records. Scores, active exploitation, patch and exploit status come straight from the sources.
IMPACT: Affected Products and Software
Affected Products
The following products are affected by CVE-2026-109927 vulnerability. Where our threat engine knows the exact affected versions, they are listed below.
| ID | VENDOR | PRODUCT | ACTION |
|---|---|---|---|
| 1 | Unknown | HIPAA Forms | View |
RED HAT CSAF/VEX: Product Impact Check
SCORING: CVSS from Multiple Sources
CVSS Scores
The Common Vulnerability Scoring System is a standardised framework for assessing the severity of vulnerabilities in software and systems. We collect and display CVSS scores from several sources for each CVE.
| SCORE | VERSION | SEVERITY | VECTOR | SOURCE |
|---|---|---|---|---|
| The sources have not yet published a verified CVSS metric. | ||||
Patch and Remediation Guide
Solution & Remediation Advisory
İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.
Public exploit and active exploitation status
Verified exploit intelligence
No verified public PoC, exploit repository or Metasploit module has been found for this CVE yet.
Weakness Classification and Attack Patterns (CWE & CAPEC)
CWE - Common Weakness Enumeration
While CVE identifies specific instances of vulnerabilities, CWE categorises the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-109927 is associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-109927 weaknesses.
Official Sources and Advisories
Yama durumu bilinmiyor
Similar Vulnerabilities
Get this vulnerability through the API
Affected products, version ranges, exploitation status and patch information in a single request, with a free key.
curl -H "x-api-key: $DAYBREACH_API_KEY" \ "https://api.daybreach.dev/api/v1/intel/cves/CVE-2026-109927"