critical CVSS 9.8

CVE-2024-4098·PHP vulnerability

The Shariff Wrapper plugin for WordPress is vulnerable to Local File Inclusion in versions up to, and including, 4.6.13 via the shariff3uu_fetch_sharecounts function. This allows unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.

Severity
critical
Software
PHP
Fixed in
4.6.14
Published
2024-06-20

Affected versions

Until: 4.6.14

Fixed in: 4.6.14

How to fix this CVE

Update the Shariff Wrapper WordPress plugin to version 4.6.14 or later to patch a critical local file inclusion vulnerability in the shariff3uu_fetch_sharecounts function. This vulnerability allows unauthenticated attackers to include and execute arbitrary PHP files, potentially leading to complete server compromise. Apply the update immediately through your WordPress plugin management interface or manually via FTP/SFTP.

sudo dnf update php php-common php-cli

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

POST|GET /wp-admin/admin-ajax.php.*action=shariff3uu_fetch_sharecounts.*(\.\.[\/\\]|php://|file://|data://|glob://|phar://)

WAF mitigation (if patching is not yet possible)

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

Block or require authentication for all requests to wp-admin/admin-ajax.php with the parameter action=shariff3uu_fetch_sharecounts. Implement strict input validation to reject requests containing directory traversal sequences (../, ..\ ) or URL scheme prefixes (php://, file://, etc.) in the function parameters.

How to check if you are affected

  1. Step 1: Verify installed Shariff Wrapper version by checking wp-content/plugins/shariff/shariff.php for the 'Version:' header field or via wp-cli: wp plugin list --field=name,version | grep shariff
  2. Step 2: Check if the plugin's shariff3uu_fetch_sharecounts function is publicly accessible by testing requests to wp-admin/admin-ajax.php?action=shariff3uu_fetch_sharecounts without authentication
  3. Step 3: Search web server access logs for suspicious patterns like '?action=shariff3uu_fetch_sharecounts' combined with file path traversal sequences (../, php://, file://): grep -i 'shariff3uu_fetch_sharecounts' /var/log/apache2/access.log /var/log/nginx/access.log
  4. Step 4: Confirm the fix by verifying the plugin version is 4.6.14 or higher and checking that the shariff.php file has been updated with the timestamp matching the security release date

Indicators of compromise

  • POST /wp-admin/admin-ajax.php?action=shariff3uu_fetch_sharecounts with path traversal patterns
  • Execution of PHP files from unexpectedlocations preceded by shariff3uu_fetch_sharecounts requests
  • Unexpected PHP process execution or webshell creation following shariff parameter requests

FAQ

What is CVE-2024-4098?

CVE-2024-4098 is a critical local file inclusion (LFI) vulnerability in the Shariff Wrapper WordPress plugin that allows unauthenticated attackers to include and execute arbitrary PHP files on the server through improper input validation in the shariff3uu_fetch_sharecounts function.

Is CVE-2024-4098 being actively exploited?

No, CVE-2024-4098 is not currently listed on the CISA KEV catalog and has no public exploit code available, but the critical CVSS score (9.8) and ease of exploitation make prompt patching essential.

What versions of the Shariff Wrapper plugin are affected by CVE-2024-4098?

All versions of the Shariff Wrapper plugin up to and including 4.6.13 are vulnerable. The vulnerability is fixed in version 4.6.14 and later.

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

Run wp plugin list --field=name,version | grep shariff on your server to check the installed version. If it shows 4.6.13 or lower, your site is vulnerable and requires immediate update.

Does Defensia detect CVE-2024-4098?

Yes — Defensia's CVE advisory scanner compares installed plugin versions against the NVD database. If the Shariff Wrapper plugin is active on a monitored WordPress site, CVE-2024-4098 will appear in your dashboard with remediation steps and priority alerts.

Related PHP CVEs

CVE-2025-25174CVSS 10Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in beeteam368 BeeTeam368 Extensions beeteam368-extensions allows PHP Local File Inclusion.This issue affects BeeTeam368 Extensions: from n/a through <= 1.9.4.
CVE-2025-46348CVSS 10YesWiki is a wiki system written in PHP. Prior to version 4.5.4, the request to commence a site backup can be performed and downloaded without authentication. The archives are created with a predictable filename, so a malicious user could create and download an archive without being authenticated. This could result in a malicious attacker making numerous requests to create archives and fill up the file system, or by downloading the archive which contains sensitive site information. This issue has been patched in version 4.5.4.
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-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-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.

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-4098. Free for 1 server.

Get started free