CVE-2025-1440

Advanced iFrame <= 2024.5 - Unauthenticated Settings Update

2025-03-25 00:00
Peter Thaleikis

Strategic Overview

Status
Patched in 2025.0
Affected Plugin
Advanced iFrame
Affected Version
<= 2024.5
CVSS
5.3Medium
Weakness type
CWE-20 · Improper Input Validation
CVE
CVE-2025-1440
View all Advanced iFrame vulnerabilities

At a glance

CVE-2025-1440 is a medium-severity Improper Input Validation vulnerability in the Advanced iFrame WordPress plugin, affecting versions <= 2024.5. 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 2025.0; sites on affected versions should update now. Disclosed March 2025, reported by Peter Thaleikis.

Vulnerability Overview

The Advanced iFrame plugin for WordPress is vulnerable to unauthorized excessive creation of options on the aip_map_url_callback() function in all versions up to, and including, 2024.5 due to insufficient restrictions. This makes it possible for unauthenticated attackers to update the advancediFrameParameterData option with an excessive amount of unvalidated data.

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-20: Improper Input Validation

Advanced iFrame <= 2024.5 carries this weakness at aip_map_url_callback(), and reaching it takes no account at all. Improper input validation means the application accepts input without confirming it has the form, type or range the code downstream assumes.

The concrete impact depends on where the unvalidated value lands, which is why records in this class range from cosmetic bugs to full compromise. For Advanced iFrame the fix is 2025.0: builds <= 2024.5 are affected, anything from 2025.0 onward is not.

Remediation

Update to version 2025.0, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Advanced iFrame 2025.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

Related records

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