CVE-2022-4057

Autoptimize <= 3.0.4 - Sensitive Information Disclosure

2022-12-05 00:00

Strategic Overview

Status: Patched in 3.1.0
Affected Plugin: Autoptimize
Affected Version: <= 3.0.4
CVSS: 5.3Medium
Weakness type: CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE: CVE-2022-4057

At a glance

CVE-2022-4057 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Autoptimize WordPress plugin, affecting versions <= 3.0.4. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.1.0; sites on affected versions should update now. Disclosed December 2022, reported by Raad Haddad.

Vulnerability Overview

The Autoptimize plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 3.0.4 via the 'ao_ccss_export_callback' and 'ao_ccss_import_callback' functions. The settings.json file is not deleted in the import/export callbacks, which could lead to the settings options being leaked. This can allow unauthenticated attackers to extract sensitive data about the plugin's 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 privileges on the target site, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Autoptimize <= 3.0.4 carries this weakness at ao_ccss_export_callback, and reaching it takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Autoptimize the fix is 3.1.0: builds <= 3.0.4 are affected, anything from 3.1.0 onward is not.

Remediation

Update to version 3.1.0, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Autoptimize 3.1.0 closes this, and updating the plugin is the step that ends it.

Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-4057 https://www.wordfence.com/threat-intel/vulnerabilities/id/5f9d237c-110e-4e71-9d2c-db99358468e6 https://nvd.nist.gov/vuln/detail/CVE-2022-4057

Related records

Other vulnerabilities in Autoptimize

CVSS Vector

5.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityLow
IntegrityNone
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/