CVE-2023-47871

Contact Form to Any API <= 1.1.6 - Missing Authorization via delete_cf7_records()

2023-11-20 00:00

Strategic Overview

Status: Patched in 1.1.7
Affected Plugin: Contact Form to Any API
Affected Version: <= 1.1.6
CVSS: 6.5Medium
Weakness type: CWE-862 · Missing Authorization
CVE: CVE-2023-47871

View all Contact Form to Any API vulnerabilities

At a glance

CVE-2023-47871 is a medium-severity Missing Authorization vulnerability in the Contact Form to Any API WordPress plugin, affecting versions <= 1.1.6. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.1.7; sites on affected versions should update now. Disclosed November 2023, reported by Arvandy.

Vulnerability Overview

The Contact Form to Any API plugin for WordPress is vulnerable to unauthorized modification/loss of data due to a missing capability check on the delete_cf7_records() function in versions up to, and including, 1.1.6. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete CF7 API entry records

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

Contact Form to Any API <= 1.1.6 carries this weakness at delete_cf7_records(), and reaching it 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 Contact Form to Any API the fix is 1.1.7: builds <= 1.1.6 are affected, anything from 1.1.7 onward is not.

Remediation

Update to version 1.1.7, 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: Contact Form to Any API 1.1.7 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-47871 https://www.wordfence.com/threat-intel/vulnerabilities/id/d4a7c647-4c57-499a-8e46-ca273985bd6d https://nvd.nist.gov/vuln/detail/CVE-2023-47871

Related records

Other vulnerabilities in Contact Form to Any API

CVSS Vector

6.5

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

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityLow
AvailabilityLow

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/