Post Grid, Slider & Carousel Ultimate – mit Shortcode, Gutenberg Block & Elementor Widget <= 1.6.10 - Authenticated (Contributor+) Lokale Datei-Inklusion über post_type_ajax_handler()

The primary impact of CVE-2024-13409 is the potential for arbitrary code execution on a WordPress server. An attacker, possessing only Contributor-level access, can exploit this vulnerability by crafting a malicious request that includes a PHP file containing arbitrary code. This code could then be executed by the web server, granting the attacker control over the affected system. The attacker could steal sensitive data, modify website content, install malware, or even gain complete control of the server. This vulnerability is particularly concerning because it requires only a low level of privilege to exploit, making it accessible to a wider range of attackers.

WordPress websites utilizing the Post Grid, Slider & Carousel Ultimate plugin, particularly those with multiple contributors or users with elevated privileges (e.g., Editor, Administrator), are at risk. Shared hosting environments where plugin installations are managed centrally are also particularly vulnerable, as a compromise of one site could potentially impact others.

• wordpress / composer / npm:

grep -r 'post_type_ajax_handler' /var/www/html/wp-content/plugins/post-grid-ultimate/

• wordpress / composer / npm:

wp plugin list | grep 'Post Grid'

• wordpress / composer / npm:

wp plugin active | grep 'Post Grid'

• wordpress / composer / npm:

curl -I http://your-wordpress-site.com/wp-content/plugins/post-grid-ultimate/ | grep -i 'theme='

1. 2025-01-24Disclosure

   disclosure

1. Reserviert2025-01-15
2. Veröffentlicht2025-01-24
3. Geändert2025-01-27
4. EPSS aktualisiert2026-04-02

The primary mitigation for CVE-2024-13409 is to upgrade the Post Grid, Slider & Carousel Ultimate plugin to a version newer than 1.6.10, where the vulnerability has been addressed. If immediate upgrading is not possible due to compatibility issues or breaking changes, consider implementing temporary workarounds. These may include restricting file access permissions on the server, implementing strict input validation on the 'theme' parameter, or using a Web Application Firewall (WAF) to block malicious requests. Monitor web server access logs for suspicious activity related to file inclusion attempts. After upgrading, confirm the fix by attempting to trigger the vulnerable endpoint with a benign file inclusion request and verifying that it is blocked or handled safely.

Aktive Installationen

1KNische

Plugin-Bewertung