CVE-2024-30512 Security Vulnerability & Exploit Details

CVE-2024-30512
Vulnerability Scoring

3.7

/10

Moderate Risk

Exploiting CVE-2024-30512 requires specific conditions, leading to a moderate security impact.

Attack Complexity Details

Attack Complexity: High
Exploits require significant effort and special conditions.
Attack Vector: Network
Vulnerability is exploitable over a network without physical access.
Privileges Required: None
No privileges are required for exploitation.
Scope: Unchanged
Exploit remains within the originally vulnerable component.
User Interaction: None
No user interaction is necessary for exploitation.

CVE-2024-30512 Details

Status: Modified

Last updated: 🕘 21 Nov 2024, 09:12 UTC
Originally published on: 🕚 09 Jun 2024, 11:15 UTC

Time between publication and last update: 164 days

CVSS Release: version 3

CVSS3 Source

audit@patchstack.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2024-30512 Vulnerability Summary

CVE-2024-30512: Missing Authorization vulnerability in weForms.This issue affects weForms: from n/a through 1.6.20.

Assessing the Risk of CVE-2024-30512

Access Complexity Graph

The exploitability of CVE-2024-30512 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2024-30512

CVE-2024-30512 presents a challenge to exploit due to its high attack complexity, but the absence of privilege requirements still makes it a viable target for skilled attackers. A thorough security review is advised.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2024-30512, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2024-30512, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

Confidentiality: Low
CVE-2024-30512 could lead to minor leaks of non-critical information without major privacy breaches.
Integrity: None
CVE-2024-30512 poses no threat to data integrity.
Availability: None
CVE-2024-30512 does not impact system availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.091% (probability of exploit)

EPSS Percentile: 41.22% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 58.78% of others.

CVE-2024-30512 References

External References

CWE Common Weakness Enumeration

CWE-862

CAPEC Common Attack Pattern Enumeration and Classification

Exploitation of Thunderbolt Protection Flaws CAPEC-665 An adversary leverages a firmware weakness within the Thunderbolt protocol, on a computing device to manipulate Thunderbolt controller firmware in order to exploit vulnerabilities in the implementation of authorization and verification schemes within Thunderbolt protection mechanisms. Upon gaining physical access to a target device, the adversary conducts high-level firmware manipulation of the victim Thunderbolt controller SPI (Serial Peripheral Interface) flash, through the use of a SPI Programing device and an external Thunderbolt device, typically as the target device is booting up. If successful, this allows the adversary to modify memory, subvert authentication mechanisms, spoof identities and content, and extract data and memory from the target device. Currently 7 major vulnerabilities exist within Thunderbolt protocol with 9 attack vectors as noted in the Execution Flow.

Vulnerable Configurations

cpe:2.3:a:weformspro:weforms:1.0.0:-:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.0.0:-:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.0.0:beta1:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.0.0:beta1:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.0.0:beta2:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.0.0:beta2:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.0.0:beta3:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.0.0:beta3:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.0.1:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.0.1:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.0.2:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.0.2:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.0.3:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.0.3:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.0.4:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.0.4:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.1.0:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.1.0:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.1.1:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.1.1:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.2.0:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.2.0:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.2.1:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.2.1:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.2.2:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.2.2:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.2.3:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.2.3:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.2.4:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.2.4:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.2.5:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.2.5:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.2.6:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.2.6:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.2.7:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.2.7:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.2.8:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.2.8:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.2.9:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.2.9:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.3.0:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.3.0:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.3.1:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.3.1:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.3.2:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.3.2:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.3.3:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.3.3:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.3.4:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.3.4:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.3.5:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.3.5:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.3.6:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.3.6:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.3.7:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.3.7:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.3.8:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.3.8:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.3.9:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.3.9:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.4.0:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.4.0:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.4.1:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.4.1:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.4.2:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.4.2:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.4.3:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.4.3:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.4.4:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.4.4:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.4.5:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.4.5:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.4.6:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.4.6:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.4.7:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.4.7:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.4.8:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.4.8:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.4.9:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.4.9:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.5.0:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.5.0:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.5.1:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.5.1:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.5.2:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.5.2:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.5.3:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.5.3:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.5.4:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.5.4:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.5.5:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.5.5:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.0:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.0:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.1:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.1:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.2:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.2:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.3:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.3:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.4:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.4:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.5:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.5:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.6:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.6:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.7:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.7:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.8:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.8:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.9:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.9:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.10:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.10:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.11:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.11:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.12:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.12:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.13:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.13:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.14:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.14:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.15:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.15:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.16:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.16:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.17:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.17:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.18:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.18:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.19:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.19:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.20:*:*:*:*:wordpress:*:*
cpe:2.3:a:weformspro:weforms:1.6.20:*:*:*:*:wordpress:*:*

Protect Your Infrastructure against CVE-2024-30512: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...
CVE-2025-2125 – A vulnerability has been found in Control iD RH iD 25.2.25.0 and classified as problematic. This vulnerability affects unknown code of the file /v2...
CVE-2025-2124 – A vulnerability, which was classified as problematic, was found in Control iD RH iD 25.2.25.0. This affects an unknown part of the file /v2/custome...

CVE-2024-30512 Vulnerability Scoring