high CVSS 8.8

CVE-2024-5630·PHP vulnerability

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.

Severity
high
Software
PHP
Fixed in
4.3000000024
Published
2024-07-15

Affected versions

Until: 4.3000000024

Fixed in: 4.3000000024

How to fix this CVE

Update the Insert or Embed Articulate Content plugin to version 4.3000000024 or later to prevent unauthorized file uploads by authenticated users. This vulnerability allows authors with upload permissions to bypass file type validation and deploy malicious PHP files, potentially leading to remote code execution. Apply the update immediately, especially on public-facing WordPress installations where multiple user accounts exist.

sudo dnf update php

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

POST /wp-admin/upload.php with Content-Disposition header containing .php extension or PHP MIME type in multipart form data, originating from authenticated user session

WAF mitigation (if patching is not yet possible)

Add this rule to your WAF to block exploitation attempts while you schedule the patch.

Implement WAF rules to restrict file uploads with PHP extensions (.php, .php3, .php4, .php5, .phtml, .pht) in the wp-content/uploads/ directory and log all upload attempts for suspicious file types. Block or challenge requests where Content-Type claims one type (e.g., image/jpeg) but filename contains executable extensions.

How to check if you are affected

  1. Step 1: Check the installed version of the Articulate plugin by logging into WordPress admin, navigating to Plugins, and locating 'Insert or Embed Articulate Content' — compare the listed version against 4.3000000024
  2. Step 2: Query the WordPress database with: `mysql -u wordpress_user -p wordpress_db -e "SELECT option_value FROM wp_options WHERE option_name='active_plugins';"` to confirm the plugin is active
  3. Step 3: Search web server logs for suspicious file uploads to wp-content/uploads/ directory: `grep -r '\.php' /var/www/html/wp-content/uploads/ | grep -v '\.php\.' | head -20`
  4. Step 4: Verify the plugin update by checking the plugin version again in WordPress admin or via database: `mysql -u wordpress_user -p wordpress_db -e "SELECT meta_value FROM wp_options WHERE option_name LIKE '%articulate%';"` after applying the patch

Indicators of compromise

  • POST requests to /wp-admin/upload.php with .php file extensions
  • Suspicious PHP files in wp-content/uploads/ directory with creation timestamps correlating to authentication logs
  • HTTP 200 responses following multipart file uploads with executable extensions

FAQ

What is CVE-2024-5630?

CVE-2024-5630 is a file upload vulnerability in the Insert or Embed Articulate Content WordPress plugin that allows authenticated users with author-level permissions to bypass file type validation and upload arbitrary files, including PHP shells, leading to remote code execution on the server.

Is CVE-2024-5630 being actively exploited?

No, according to CISA KEV data, CVE-2024-5630 is not currently being actively exploited in the wild. However, no public exploits are required since the vulnerability is straightforward to exploit by any authenticated user.

What versions of the Articulate plugin are affected by CVE-2024-5630?

All versions of the Insert or Embed Articulate Content plugin prior to version 4.3000000024 are vulnerable. Users must upgrade to 4.3000000024 or later to remediate the issue.

How do I check if my WordPress site is vulnerable to CVE-2024-5630?

Log into your WordPress dashboard, navigate to Plugins, and check the version number of 'Insert or Embed Articulate Content'. If the version is lower than 4.3000000024, your site is vulnerable. You can also use the WP-CLI command: `wp plugin get articulate-content-iframe --field=version`

Does Defensia detect CVE-2024-5630?

Yes — Defensia's CVE advisory scanner compares installed WordPress plugin versions against the NVD database. If the Insert or Embed Articulate Content plugin is installed on a monitored server, CVE-2024-5630 will appear in your dashboard with remediation steps.

Related PHP CVEs

CVE-2026-39337CVSS 10ChurchCRM is an open-source church management system. Prior to 7.1.0, critical pre-authentication remote code execution vulnerability in ChurchCRM's setup wizard allows unauthenticated attackers to inject arbitrary PHP code during the initial installation process, leading to complete server compromise. The "$dbPassword" variable is not sanitized. This vulnerability exists due to an incomplete fix for CVE-2025-62521. This vulnerability is fixed in 7.1.0.
CVE-2024-5932CVSS 10The GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.14.1 via deserialization of untrusted input from the 'give_title' parameter. This makes it possible for unauthenticated attackers to inject a PHP Object. The additional presence of a POP chain allows attackers to execute code remotely, and to delete arbitrary files.
CVE-2026-28289CVSS 10FreeScout is a free help desk and shared inbox built with PHP's Laravel framework. A patch bypass vulnerability for CVE-2026-27636 in FreeScout 1.8.206 and earlier allows any authenticated user with file upload permissions to achieve Remote Code Execution (RCE) on the server by uploading a malicious .htaccess file using a zero-width space character prefix to bypass the security check. The vulnerability exists in the sanitizeUploadedFileName() function in app/Http/Helper.php. The function contains a Time-of-Check to Time-of-Use (TOCTOU) flaw where the dot-prefix check occurs before sanitization removes invisible characters. This vulnerability is fixed in 1.8.207.
CVE-2025-62521CVSS 10ChurchCRM is an open-source church management system. Prior to version 5.21.0, a pre-authentication remote code execution vulnerability in ChurchCRM's setup wizard allows unauthenticated attackers to inject arbitrary PHP code during the initial installation process, leading to complete server compromise. The vulnerability exists in `setup/routes/setup.php` where user input from the setup form is directly concatenated into a PHP configuration template without any validation or sanitization. Any parameter in the setup form can be used to inject PHP code that gets written to `Include/Config.php`, which is then executed on every page load. This is more severe than typical authenticated RCE vulnerabilities because it requires no credentials and affects the installation process that administrators must complete. Version 5.21.0 patches the issue.
CVE-2025-47916CVSS 10Invision Community 5.0.0 before 5.0.7 allows remote code execution via crafted template strings to themeeditor.php. The issue lies within the themeeditor controller (file: /applications/core/modules/front/system/themeeditor.php), where a protected method named customCss can be invoked by unauthenticated users. This method passes the value of the content parameter to the Theme::makeProcessFunction() method; hence it is evaluated by the template engine. Accordingly, this can be exploited by unauthenticated attackers to inject and execute arbitrary PHP code by providing crafted template strings.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-5630. Free for 1 server.

Get started free