LiveActive security incident?Get immediate response
CVE Record

CVE-2024-8420: DHVC Form <= 2.4.7 - Unauthenticated Privilege Escalation

The DHVC Form plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 2.4.7. This is due to the plugin allowing a user to supply the 'role' field when registering. This makes it possible for unauthenticated attackers to register as an administrator on sites.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2024-8420 lets unauthenticated visitors create WordPress accounts with administrator privileges on sites using DHVC Form versions up to 2.4.7. For executives, this is urgent because it can hand full site control to an outside attacker without credentials or user interaction.

Executive priority

Treat as immediate-priority for any internet-facing WordPress site using DHVC Form. The business risk is full website compromise, including content tampering, credential theft, malware placement, and operational disruption.

Technical view

The DHVC Form WordPress plugin improperly allows the registration request to supply a role value. In affected versions through 2.4.7, an unauthenticated attacker can register as an administrator. The CVSS 3.1 score is 9.8, with network attack vector, low complexity, no privileges, and no user interaction.

Likely exposure

Exposure is limited to WordPress sites running SiteSao DHVC Form up to and including version 2.4.7, especially where public registration or plugin registration forms are reachable.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. The vulnerability is still high-risk because the described path is remote, unauthenticated, low-complexity, and can grant administrator access.

Researcher notes

Evidence comes from the CVE record and Wordfence advisory. The bundle names the vulnerable behavior and affected range but does not provide a confirmed fixed version, active exploitation evidence, or detailed vendor remediation instructions.

Mitigation direction

  • Inventory WordPress sites for DHVC Form and record plugin versions.
  • Disable or remove DHVC Form versions up to 2.4.7 until vendor guidance is confirmed.
  • Check the vendor marketplace and Wordfence advisory for fixed-version guidance.
  • Audit WordPress administrator accounts for unauthorized registrations.
  • Restrict public registration where it is not business-critical.

Validation and detection

  • Confirm whether DHVC Form is installed on each WordPress property.
  • Verify installed versions against the affected range through 2.4.7.
  • Review recent WordPress administrator accounts for unexpected creation events.
  • Inspect registration-related logs for suspicious role-field activity.
  • Document whether the plugin is disabled, removed, or remediated.
Prepared
Confidence
medium
Sources
4

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 · low confidence lookup

CWE-266: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-8420 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

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
3Source 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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2024-8420Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
SiteSaoDHVC Form0unaffected
Weakness

CWE details

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

CWE-266 · source CWE mapping

Incorrect Privilege Assignment

Incorrect Privilege Assignment represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.