BerqWP Plugin up to 2.2.53 on WordPress authorization

Summaryinfo

A vulnerability identified as problematic has been detected in BerqWP Plugin up to 2.2.53 on WordPress. This issue affects some unknown processing. This manipulation causes authorization. This vulnerability is tracked as CVE-2025-58979. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability has been found in BerqWP Plugin up to 2.2.53 on WordPress and classified as problematic. Affected by this vulnerability is some unknown functionality. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect integrity. The summary by CVE is:

Missing Authorization vulnerability in BerqWP BerqWP allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects BerqWP: from n/a through 2.2.53.

The weakness was disclosed by Bao. The advisory is shared at patchstack.com. This vulnerability is known as CVE-2025-58979 since 09/06/2025. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/09/2025).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• WordPress Plugin

Name

• BerqWP Plugin

Version

• 2.2.0
• 2.2.1
• 2.2.2
• 2.2.3
• 2.2.4
• 2.2.5
• 2.2.6
• 2.2.7
• 2.2.8
• 2.2.9
• 2.2.10
• 2.2.11
• 2.2.12
• 2.2.13
• 2.2.14
• 2.2.15
• 2.2.16
• 2.2.17
• 2.2.18
• 2.2.19
• 2.2.20
• 2.2.21
• 2.2.22
• 2.2.23
• 2.2.24
• 2.2.25
• 2.2.26
• 2.2.27
• 2.2.28
• 2.2.29
• 2.2.30
• 2.2.31
• 2.2.32
• 2.2.33
• 2.2.34
• 2.2.35
• 2.2.36
• 2.2.37
• 2.2.38
• 2.2.39
• 2.2.40
• 2.2.41
• 2.2.42
• 2.2.43
• 2.2.44
• 2.2.45
• 2.2.46
• 2.2.47
• 2.2.48
• 2.2.49
• 2.2.50
• 2.2.51
• 2.2.52
• 2.2.53

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion