CVE-2024-5541

Ibtana - WordPress Website Builder <= 1.2.3.3 - Unauthenticated reCAPTCHA Settings Update

2024-06-17 14:09
Peter Thaleikis

Strategic Overview

Status
Patched in 1.2.3.4
Affected Plugin
Ibtana – WordPress Website Builder
Affected Version
<= 1.2.3.3
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-5541
View all Ibtana – WordPress Website Builder vulnerabilities

At a glance

CVE-2024-5541 is a medium-severity Missing Authorization vulnerability in the Ibtana WordPress plugin, affecting versions <= 1.2.3.3. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.2.3.4; sites on affected versions should update now. Disclosed June 2024, reported by Peter Thaleikis.

Vulnerability Overview

The Ibtana – WordPress Website Builder plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'ibtana_visual_editor_register_ajax_json_endpont' function in all versions up to, and including, 1.2.3.3. This makes it possible for unauthenticated attackers to update option values for reCAPTCHA keys on the WordPress site. This can be leveraged to bypass reCAPTCHA on the site. CVE-2024-37123 is likely a duplicate of this issue.

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, and no interaction from a victim user.

CWE-862: Missing Authorization

Ibtana <= 1.2.3.3 carries this weakness at ibtana_visual_editor_register_ajax_json_endpont, and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Ibtana the fix is 1.2.3.4: builds <= 1.2.3.3 are affected, anything from 1.2.3.4 onward is not.

Remediation

Update to version 1.2.3.4, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Ibtana 1.2.3.4 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-5541https://www.wordfence.com/threat-intel/vulnerabilities/id/e022febe-7295-493d-afa7-185f55b4d3b9https://nvd.nist.gov/vuln/detail/CVE-2024-5541

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C