dbcve.org
IbtanaWordPress extension · Vowelweb

CVE-2024-5541

MEDIUM · 5.3 CVSS v3.1 Published 2024-06-18
Fix available
A fix is available. Upgrade to after 1.2.3.3 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Ibtana WordPress Website Builder plugin has a missing capability check on the 'ibtana_visual_editor_register_ajax_json_endpont' AJAX endpoint. This allows unauthenticated attackers to call this function and modify WordPress options directly, specifically targeting reCAPTCHA keys. By overwriting the reCAPTCHA configuration, attackers can disable reCAPTCHA protection entirely, enabling automated abuse, spam, and brute-force attacks against the site.

MitigationUpdate the Ibtana plugin to the latest version once a patch is released. Until then, consider disabling the plugin or implementing alternative protective measures such as WAF rules blocking the vulnerable endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IbtanaWordPress extension
Affected:<= 1.2.3.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Ibtana plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Ibtana' or 'Ibtana WordPress Website Builder' by Vowelweb
    Affected if The Ibtana plugin appears in the list of installed plugins
  2. Check installed plugin version
    In Plugins list, click on the Ibtana plugin to view details, or inspect the plugin header in wp-content/plugins/ibtana/ibtana.php for the Version field
    Affected if The installed version is 1.2.3.3 or lower (any version <= 1.2.3.3)
  3. Verify AJAX endpoint is accessible
    Send a POST request to wp-admin/admin-ajax.php with action=ibtana_visual_editor_register_ajax_json_endpoint without authentication (no nonce or logged-in session). Use a tool like curl: curl -X POST https://yourdomain.com/wp-admin/admin-ajax.php -d 'action=ibtana_visual_editor_register_ajax_json_endpoint'
    Affected if The endpoint returns a valid response (200 OK) instead of requiring authentication or returning a permission error
  4. Inspect reCAPTCHA configuration options
    In WordPress admin, navigate to the plugin settings where reCAPTCHA is configured (typically under Ibtana settings or WordPress options table in database). Check the recaptcha_enable option and associated keys in wp_options table
    Affected if reCAPTCHA settings have been changed, keys have been overwritten, or recaptcha_enable is set to disabled (0 or empty) when you did not make those changes)
  5. Check for signs of exploitation in logs
    Review server access logs and WordPress audit logs for requests to admin-ajax.php with the action=ibtana_visual_editor_register_ajax_json_endpoint parameter, especially from unexpected IP addresses
    Affected if There are unauthenticated requests to this endpoint in your logs

You are affected if the Ibtana plugin version is 1.2.3.3 or lower AND the vulnerable AJAX endpoint responds to unauthenticated requests, allowing potential modification of reCAPTCHA settings.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 1.2.3.3
Interim mitigation

Update the Ibtana plugin to the latest version once a patch is released. Until then, consider disabling the plugin or implementing alternative protective measures such as WAF rules blocking the vulnerable endpoint.

Fix this in Ibtana Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5541 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-5541 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data