CVE-2024-0756VulnerabilityPublished 4 Jun 2024Updated 3 Mar 2026

CVE-2024-0756: Insert or Embed Articulate Content into WordPress · Insufficient Verification of Data Authenticity

Affects Insert or Embed Articulate Content into WordPressSource CVE Database V5

Not known to be exploited · CVSS 3.5 Low.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

3.5Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Insert or Embed Articulate Content into WordPress	Affected =0	Fixed in–

AI-suggested

To mitigate CVE-2024-0756, organizations should first restrict plugin usage to trusted users with appropriate privileges to minimize the risk of malicious iframe injection. Administrators should implement strict content security policies (CSP) that limit the domains from which iframes can be loaded, effectively blocking unauthorized external content. Until an official patch is released, consider disabling or removing the Insert or Embed Articulate Content plugin if it is not essential. For sites requiring iframe embedding, use alternative plugins or methods that enforce strict URL validation and sanitization. Regularly audit user-generated content for unauthorized iframe elements and monitor site behavior for unusual iframe loads. Educate users about the risks of embedding untrusted content and enforce strong authentication and user activity monitoring to detect suspicious actions. Once a patch or update is available from the plugin developer, apply it promptly. Additionally, maintain up-to-date backups and incident response plans to recover quickly if exploitation occurs.

Description

The Insert or Embed Articulate Content into WordPress plugin through 4.3000000023 lacks validation of URLs when adding iframes, allowing attackers to inject an iFrame in the page and thus load arbitrary content from any page.

Impact

The primary impact of CVE-2024-0756 is on the integrity of website content, as attackers can inject arbitrary iframes that load external content. This can lead to content spoofing, misleading users, or embedding malicious content such as phishing pages or drive-by downloads. Although confidentiality and availability are not directly affected, the presence of malicious iframes can damage user trust and the reputation of affected websites. The requirement for authenticated access and user interaction reduces the risk of widespread automated exploitation but does not eliminate targeted attacks, especially in environments with multiple users or contributors. Organizations relying on this plugin for content embedding may face increased risk of website defacement or indirect compromise through malicious iframe content. The lack of a patch increases exposure time, and the vulnerability could be exploited in combination with social engineering or other attack vectors. Overall, the impact is moderate for organizations with active WordPress sites using this plugin, particularly those with multiple contributors or less restrictive user permissions.

CWE-345Insufficient Verification of Data Authenticity (opens in a new tab)
Class weaknessOWASP Top 10 A08:2025: Software or Data Integrity Failures (opens in a new tab)
The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
OWASP Cheat Sheets
XML Security (opens in a new tab)
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
REST Assessment (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.2 (opens in a new tab)
V3.5.3 (opens in a new tab)
V13.2.6 (opens in a new tab)
Attack patterns
JSON Hijacking (aka JavaScript Hijacking) (opens in a new tab)
Cache Poisoning (opens in a new tab)
DNS Cache Poisoning (opens in a new tab)
Spoofing of UDDI/ebXML Messages (opens in a new tab)
Application API Message Manipulation via Man-in-the-Middle (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

wpscan.com/vulnerability/9130a42d-fca3-4f9c-ab97-d5e0a7a5cef2/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Mar 2026, 17:29 UTC

WeaknessesCWE-345

Technical details

References

Community reviews

Related threats