{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-0756 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-0756 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-0756 is a low-severity cross-site scripting vulnerability in Unknown Insert or Embed Articulate Content into WordPress, published on 4 Jun 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-0756 and fix it if it is affected.\n\nWhat it is: CVE-2024-0756 is a low-severity cross-site scripting vulnerability in Unknown Insert or Embed Articulate Content into WordPress, published on 4 Jun 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-0756 in the wild and no public exploit code.\n\nAffected product: Unknown Insert or Embed Articulate Content into WordPress. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-0756/ (Markdown: https://insights.sbomify.com/CVE-2024-0756/index.md)","id":"CVE-2024-0756","markdown":"https://insights.sbomify.com/CVE-2024-0756/index.md","name":"CVE-2024-0756","record":{"aliases":["GHSA-5jjj-4rqq-qph2"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Attackers can inject arbitrary iframes into WordPress pages via the Articulate Content plugin, potentially executing malicious scripts or loading harmful content.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"insert_or_embed_articulate_content","vendor":"elearningfreak"}],"cvss":{"score":3.5,"severity":"low","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Insert or Embed Articulate Content into WordPress \u003c= 4.3000000023 - Iframe Injection","id":"CVE-2024-0756","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Insert or Embed Articulate Content into WordPress \u003c= 4.3000000023 - Author+ Upload to RCE","id":"CVE-2024-0757"},"packages":[],"prev":{"headline":"Memory corruption in Firefox","id":"CVE-2024-0755"},"products":["Insert or Embed Articulate Content into WordPress"],"published":"2024-06-04","related":[{"cvss_score":8.8,"headline":"Insert or Embed Articulate Content into WordPress \u003c 4.3000000024 - Author+ Arbitrary File Upload","id":"CVE-2024-5630","kev_date_added":null,"published":"2024-07-15"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2019-15649","kev_date_added":null,"published":"2019-08-27"},{"cvss_score":6.5,"headline":"Cross-site scripting in Insert or Embed Articulate Content into WordPress","id":"CVE-2023-50824","kev_date_added":null,"published":"2023-12-21"},{"cvss_score":6.5,"headline":"Missing authorization in n/a","id":"CVE-2019-15648","kev_date_added":null,"published":"2019-08-27"},{"cvss_score":5.4,"headline":"Insert or Embed Articulate Content into WordPress \u003c= 4.3000000023 - Author+ Upload to RCE","id":"CVE-2024-0757","kev_date_added":null,"published":"2024-06-04"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-03","vendors":["Unknown"]},"summary":"Attackers can inject arbitrary iframes into WordPress pages via the Articulate Content plugin, potentially executing malicious scripts or loading harmful content.","url":"https://insights.sbomify.com/CVE-2024-0756/"}