CVE-2024-31243: WordPress Bricksforge plugin <= 2.0.17 - Unauthenticated Arbitrary WordPress Setting Deletion vulnerability
Published Jun 9, 2024
·Updated
Missing Authorization vulnerability in Bricksforge.This issue affects Bricksforge: from n/a through 2.0.17.
Affected Software
1 affected component
Bricksforge Bricksforge Wordpress<2.1.1
Remediation
Information
Update to 2.1.1 or a higher version.
Event History
Jun 9, 2024
CVE Published
via MITRE·11:06 AM
Data Sourced
via MITRE·11:06 AM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·12:15 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2024-31243?
CVE-2024-31243 is considered a critical vulnerability due to its nature of missing authorization that can lead to unauthorized access.
2
How do I fix CVE-2024-31243?
To mitigate CVE-2024-31243, update Bricksforge to version 2.0.18 or later as this version addresses the authorization issue.
3
Which versions are affected by CVE-2024-31243?
CVE-2024-31243 affects Bricksforge versions prior to 2.0.18, specifically from n/a through 2.0.17.
4
What type of vulnerability is identified in CVE-2024-31243?
CVE-2024-31243 is classified as a missing authorization vulnerability, allowing unauthorized actions within the system.
5
Is there a workaround for CVE-2024-31243?
There are no known workarounds for CVE-2024-31243; the recommended action is to upgrade to the fixed version.