CVE-2023-6369

Export WP Page to Static HTML/CSS <= 2.1.9 - Missing Authorization via Multiple AJAX Actions

2023-11-28 00:00
Alex Thomas

Strategic Overview

Status
Patched in 2.2.0
Affected Plugin
Export WordPress Pages to Static HTML & PDF — Static Site Export
Affected Version
<= 2.1.9
CVSS
5.4Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2023-6369
View all Export WordPress Pages to Static HTML & PDF — Static Site Export vulnerabilities

At a glance

CVE-2023-6369 is a medium-severity Missing Authorization vulnerability in the Export WordPress Pages to Static HTML & PDF WordPress plugin, affecting versions <= 2.1.9. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 2.2.0; sites on affected versions should update now. Disclosed November 2023, reported by Alex Thomas.

Vulnerability Overview

The Export WP Page to Static HTML/CSS plugin for WordPress is vulnerable to unauthorized access of data and modification of data due to a missing capability check on multiple AJAX actions in all versions up to, and including, 2.1.9. This makes it possible for authenticated attackers, with subscriber-level access and above, to disclose sensitive information or perform unauthorized actions, such as saving advanced plugin settings.

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-862: Missing Authorization

Reaching this weakness in Export WordPress Pages to Static HTML & PDF <= 2.1.9 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Export WordPress Pages to Static HTML & PDF the fix is 2.2.0: builds <= 2.1.9 are affected, anything from 2.2.0 onward is not.

Remediation

Update to version 2.2.0, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Export WordPress Pages to Static HTML & PDF 2.2.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-6369https://www.wordfence.com/threat-intel/vulnerabilities/id/47cb48aa-b556-4f25-ac68-ff0a812972c1https://nvd.nist.gov/vuln/detail/CVE-2023-6369

Related records

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