CVE-2019-15113

Companion Sitemap Generator – HTML & XML <= 3.6.6 - Cross-Site Request Forgery and Local File Inclusion

2019-01-10 00:00
Anonymous

Strategic Overview

Status
Patched in 3.7.0
Affected Version
<= 3.6.6
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2019-15113
View all Companion Sitemap Generator – Simple, Smart, and SEO-Ready vulnerabilities

At a glance

CVE-2019-15113 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Companion Sitemap Generator WordPress plugin, affecting versions <= 3.6.6. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.7.0; sites on affected versions should update now. Disclosed January 2019.

Vulnerability Overview

The Companion Sitemap Generator plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.6.6. This makes it possible for unauthenticated attackers to modify the plugin settings or include any local file with a PHP extension via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Companion Sitemap Generator <= 3.6.6 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Companion Sitemap Generator the fix is 3.7.0: builds <= 3.6.6 are affected, anything from 3.7.0 onward is not.

Remediation

Update to version 3.7.0, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Companion Sitemap Generator: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Companion Sitemap Generator 3.7.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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