CVE-2024-37490

Bard <= 2.210 - Cross-Site Request Forgery to Notice Dismissal

2024-07-04 00:00

Strategic Overview

Status: Patched in 2.211
Affected Theme: Bard
Affected Version: <= 2.210
CVSS: 4.3Medium
Weakness type: CWE-352 · Cross-Site Request Forgery (CSRF)
CVE: CVE-2024-37490

At a glance

CVE-2024-37490 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Bard WordPress theme, affecting versions <= 2.210. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.211; sites on affected versions should update now. Disclosed July 2024, reported by Dhabaleshwar Das.

Vulnerability Overview

The Bard theme for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.210. This is due to missing or incorrect nonce validation on the bard_activation_notice() function. This makes it possible for unauthenticated attackers to dismiss notices via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Bard <= 2.210 carries this weakness at bard_activation_notice(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Bard the fix is 2.211: builds <= 2.210 are affected, anything from 2.211 onward is not.

Remediation

Update to version 2.211, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Bard: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Bard 2.211 closes this, and updating the theme is the step that ends it.

Firewall
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-37490 https://www.wordfence.com/threat-intel/vulnerabilities/id/cec0ba0e-28a5-46c0-97c2-bbf73bd2dbad https://nvd.nist.gov/vuln/detail/CVE-2024-37490

Related records

Other vulnerabilities in Bard

CVSS Vector

4.3

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

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionRequired
ScopeUnchanged
ConfidentialityNone
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/