CVE-2022-2314

VR Calendar <= 2.3.1 - Unauthenticated Remote Code Execution

2022-07-22 00:00
Vinay Varma Mudunuri

Strategic Overview

Status
Patched in 2.3.2
Affected Plugin
VR Calendar
Affected Version
<= 2.3.1
CVSS
9.8Critical
Weakness type
CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE
CVE-2022-2314
View all VR Calendar vulnerabilities

At a glance

CVE-2022-2314 is a critical-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the VR Calendar WordPress plugin, affecting versions <= 2.3.1. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.3.2; sites on affected versions should update now. Disclosed July 2022, reported by Vinay Varma Mudunuri.

Vulnerability Overview

The VR Calendar plugin for WordPress is vulnerable to Remote Code Execution in versions up to, and including, 2.2.2 via the handleCommands() function that accepts user supplied input via the 'vrc_cmd' parameter that is passed to call_user_func(). This allows unauthenticated attackers to execute code on the server.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

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

VR Calendar <= 2.3.1 carries this weakness at vrc_cmd, 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 VR Calendar the fix is 2.3.2: builds <= 2.3.1 are affected, anything from 2.3.2 onward is not.

Remediation

Update to version 2.3.2, 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: VR Calendar 2.3.2 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-2022-2314https://www.wordfence.com/threat-intel/vulnerabilities/id/bf2a57fa-28f8-4fd0-814b-a4c9ae77817ahttps://nvd.nist.gov/vuln/detail/CVE-2022-2314

Related records

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