CVE-2023-51483

WP Frontend Profile <= 1.3.1 - Unauthenticated Privilege Escalation

2023-12-27 00:00

Strategic Overview

Status: Patched in 1.3.2
Affected Plugin: WP Frontend Profile
Affected Version: <= 1.3.1
CVSS: 9.8Critical
Weakness type: CWE-862 · Missing Authorization
CVE: CVE-2023-51483

View all WP Frontend Profile vulnerabilities

At a glance

CVE-2023-51483 is a critical-severity Missing Authorization vulnerability in the WP Frontend Profile WordPress plugin, affecting versions <= 1.3.1. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.3.2; sites on affected versions should update now. Disclosed December 2023, reported by Rafie Muhammad.

Vulnerability Overview

The WP Frontend Profile plugin for WordPress is vulnerable to privilege in all versions up to, and including, 1.3.1. This makes it possible for unauthenticated attackers to take over arbitrary accounts on the site.

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

CWE-862: Missing Authorization

Reaching this weakness in WP Frontend Profile <= 1.3.1 takes no account at all. 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 WP Frontend Profile the fix is 1.3.2: builds <= 1.3.1 are affected, anything from 1.3.2 onward is not.

Remediation

Update to version 1.3.2, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WP Frontend Profile 1.3.2 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-51483 https://www.wordfence.com/threat-intel/vulnerabilities/id/91de6cf4-e5df-4130-bb96-92b89717a678 https://nvd.nist.gov/vuln/detail/CVE-2023-51483

Related records

Same weakness class

Other vulnerabilities in WP Frontend Profile

CVSS Vector

9.8

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

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

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/