CVE-2019-15713

My Calendar <= 3.1.9 - Unauthenticated Cross-Site Scripting

2019-04-30 00:00
Anonymous

Strategic Overview

Status
Patched in 3.1.10
Affected Version
<= 3.1.9
CVSS
6.1Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2019-15713
View all My Calendar – Accessible Event Manager vulnerabilities

At a glance

CVE-2019-15713 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the My Calendar WordPress plugin, affecting versions <= 3.1.9. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.1.10; sites on affected versions should update now. Disclosed April 2019.

Vulnerability Overview

The my-calendar plugin before 3.1.10 for WordPress has XSS.

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.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in My Calendar <= 3.1.9 takes no account at all. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For My Calendar the fix is 3.1.10: builds <= 3.1.9 are affected, anything from 3.1.10 onward is not.

Remediation

Update to version 3.1.10, 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. None of that substitutes for the fix: My Calendar 3.1.10 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

Related records

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