CVE-2024-11002

InPost Gallery <= 2.1.4.2 - Authenticated (Subscriber+) Arbitrary Shortcode Execution via inpost_gallery_get_shortcode_template

2024-11-25 17:51
Arkadiusz Hydzik

Strategic Overview

Status
Patched in 2.1.4.3
Affected Plugin
InPost Gallery
Affected Version
<= 2.1.4.2
CVSS
6.3Medium
Weakness type
CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE
CVE-2024-11002
View all InPost Gallery vulnerabilities

At a glance

CVE-2024-11002 is a medium-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the InPost Gallery WordPress plugin, affecting versions <= 2.1.4.2. It carries a CVSS score of 6.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.1.4.3; sites on affected versions should update now. Disclosed November 2024, reported by Arkadiusz Hydzik.

Vulnerability Overview

The The InPost Gallery plugin for WordPress is vulnerable to arbitrary shortcode execution via the inpost_gallery_get_shortcode_template AJAX action in all versions up to, and including, 2.1.4.2. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for authenticated attackers, with Subscriber-level access and above, to execute arbitrary shortcodes.

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.

CWE-94: Improper Control of Generation of Code ('Code Injection')

Reaching this weakness in InPost Gallery <= 2.1.4.2 takes an account at Subscriber level or above. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.

The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For InPost Gallery the fix is 2.1.4.3: builds <= 2.1.4.2 are affected, anything from 2.1.4.3 onward is not.

Remediation

Update to version 2.1.4.3, or a newer patched version

How does WordSec protect against this?

An attacker needs Subscriber 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: InPost Gallery 2.1.4.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-11002https://www.wordfence.com/threat-intel/vulnerabilities/id/5fbb2dcf-38b8-4ef1-bfea-bf5872cc7e37https://nvd.nist.gov/vuln/detail/CVE-2024-11002

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C