The Insert or Embed Articulate Content into WordPress plugin before 4.3000000024 does not prevent authors from uploading arbitrary files to the site, which may allow them to upload PHP shells on affected sites.
Product
elearningfreak insert or embed articulate content vulnerabilities
6 published CVES affecting elearningfreak insert or embed articulate content, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 6
- Critical
- 0
- High
- 2
- Medium
- 4
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest elearningfreak insert or embed articulate content CVEs
Newest publication first
-
HighCVSS 8.8 EPSS 0.68%
-
CVE-2024-0756 Insert or Embed Articulate Content into WordPress <= 4.3000000023 - Iframe Injection
PublishedMediumCVSS 5.4 EPSS 0.20%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.
-
MediumCVSS 5.4 EPSS 0.94%
The Insert or Embed Articulate Content into WordPress plugin through 4.3000000023 is not properly filtering which file extensions are allowed to be imported on the server, allowing the uploading of malicious code within zip files
-
MediumCVSS 5.4 EPSS 0.31%
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Brian Batt Insert or Embed Articulate Content into WordPress allows Stored XSS.This issue affects Insert or Embed Articulate Content into WordPress: from n/a through 4.3000000021...
-
CVE-2019-15649 Insert or Embed Articulate Content into WordPress < 4.2999 - Arbitrary File Upload
PublishedHighCVSS 8.8 EPSS 1.7%The insert-or-embed-articulate-content-into-wordpress plugin before 4.2999 for WordPress has insufficient restrictions on file upload.
-
CVE-2019-15648 Insert or Embed Articulate Content into WordPress < 4.29991 - Directory Traversal
PublishedMediumCVSS 6.5 EPSS 0.63%The insert-or-embed-articulate-content-into-wordpress plugin before 4.29991 for WordPress has insufficient restrictions on deleting or renaming by a Subscriber.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.