CVE-2026-85113

GiveWP <= 4.16.8 - Unauthenticated Arbitrary Shortcode Execution

2026-09-18 00:00
Jakub Herman

Strategic Overview

Status
Patched in 4.16.9
Affected Plugin
GiveWP – Donation Plugin and Fundraising Platform
Affected Version
<= 4.16.8
CVSS
6.5Medium
Weakness type
CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE
CVE-2026-85113
View all GiveWP – Donation Plugin and Fundraising Platform vulnerabilities

At a glance

CVE-2026-85113 is a medium-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the GiveWP WordPress plugin, affecting versions <= 4.16.8. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.16.9; sites on affected versions should update now. Disclosed September 2026, reported by Jakub Herman.

Vulnerability Overview

The GiveWP plugin for WordPress is vulnerable to Arbitrary Shortcode Execution in all versions up to, and including, 4.16.8. This is due to the use of do_shortcode() on user supplied input. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes registered on the site. The impact depends on which shortcodes the site has registered, so a site running a plugin whose shortcodes expose data or perform actions is affected more severely.

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 privileges on the target site, and no interaction from a victim user.

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

GiveWP <= 4.16.8 carries this weakness at do_shortcode(), and reaching it takes no account at all. 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 GiveWP the fix is 4.16.9: builds <= 4.16.8 are affected, anything from 4.16.9 onward is not.

Remediation

Update to version 4.16.9, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: 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: GiveWP 4.16.9 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

https://www.cve.org/CVERecord?id=CVE-2026-85113https://www.wordfence.com/threat-intel/vulnerabilities/id/1d59151c-aa50-4183-b429-143580961cb1https://nvd.nist.gov/vuln/detail/CVE-2026-85113

Related records

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