Insert or Embed Articulate Content into WordPress <= 4.3000000025 - Authenticated (Editor+) Arbitrary File Upload
Strategic Overview
- Status
- Patched in 4.3000000026
- Affected Plugin
- Insert or Embed Articulate Content into WordPress
- Affected Version
<= 4.3000000025- CVSS
- 7.2High
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2025-32202
At a glance
CVE-2025-32202 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Insert or Embed Articulate Content into WordPress WordPress plugin, affecting versions <= 4.3000000025. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Editor level or above. The issue is fixed in version 4.3000000026; sites on affected versions should update now. Disclosed April 2025, reported by Phan Trong Quan.
Vulnerability Overview
The Insert or Embed Articulate Content into WordPress plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in all versions up to, and including, 4.3000000025. This makes it possible for authenticated attackers, with Editor-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.
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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-434: Unrestricted Upload of File with Dangerous Type
Reaching this weakness in Insert or Embed Articulate Content into WordPress <= 4.3000000025 takes an account at Editor level or above. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.
If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For Insert or Embed Articulate Content into WordPress the fix is 4.3000000026: builds <= 4.3000000025 are affected, anything from 4.3000000026 onward is not.
Remediation
Update to version 4.3000000026, or a newer patched version
How does WordSec protect against this?
An attacker needs Editor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Insert or Embed Articulate Content into WordPress 4.3000000026 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Insert or Embed Articulate Content into WordPress
- 8.8Freemius SDK <= 2.2.3 Arbitrary Options Update
- 6.5CVE-2019-15648: Insert or Embed Articulate… Directory Traversal
CVE-2019-15648 - 6.4CVE-2024-0756: Insert or Embed Articulate Content… Stored XSS
CVE-2024-0756 - 6.4CVE-2023-50824: Insert or Embed Articulate Content… Stored XSS
CVE-2023-50824 - 6.3CVE-2022-4974: Freemius SDK <= 2.4.2 Missing Authorization Checks
CVE-2022-4974 - 6.1CVE-2023-33999: Freemius SDK <= 2.5.9 Reflected Cross-Site Scripting
CVE-2023-33999
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C