CVE-2022-45852

WP-FormAssembly <= 2.0.5 - Authenticated (Contributor+) Arbitrary File Read

2022-11-23 00:00

Strategic Overview

Status: Patched in 2.0.6
Affected Plugin: WP-FormAssembly
Affected Version: <= 2.0.5
CVSS: 6.5Medium
Weakness type: CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE: CVE-2022-45852

View all WP-FormAssembly vulnerabilities

At a glance

CVE-2022-45852 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WP-FormAssembly WordPress plugin, affecting versions <= 2.0.5. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.0.6; sites on affected versions should update now. Disclosed November 2022, reported by Tien Nguyen Ahn.

Vulnerability Overview

The WP-FormAssembly plugin for WordPress is vulnerable to Arbitrary File Read in versions up to, and including, 2.0.5. This is due to insufficient controls on defining file paths on the fa_add() function. This makes it possible for contributor-level attackers to read the contents of any server file, including database configurations.

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. A successful exploit has high impact on confidentiality.

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

WP-FormAssembly <= 2.0.5 carries this weakness at fa_add(), and reaching it takes an account at Contributor level or above. 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 WP-FormAssembly the fix is 2.0.6: builds <= 2.0.5 are affected, anything from 2.0.6 onward is not.

Remediation

Update to version 2.0.6, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: WP-FormAssembly 2.0.6 closes this, and updating the plugin is the step that ends it.

Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-45852 https://www.wordfence.com/threat-intel/vulnerabilities/id/724a1790-811a-4ec5-a664-a22e6b72fba1 https://nvd.nist.gov/vuln/detail/CVE-2022-45852

Related records

Other vulnerabilities in WP-FormAssembly

CVSS Vector

6.5

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

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
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/