Magazine3 PWA for WP & AMP Plugin up to 1.7.72 on WordPress authorization

Summaryinfo

A vulnerability marked as problematic has been reported in Magazine3 PWA for WP & AMP Plugin up to 1.7.72 on WordPress. Affected is an unknown function. This manipulation causes authorization. This vulnerability appears as CVE-2024-47318. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability classified as problematic was found in Magazine3 PWA for WP & AMP Plugin up to 1.7.72 on WordPress. Affected by this vulnerability is an unknown code. 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 Magazine3 PWA for WP & AMP allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects PWA for WP & AMP: from n/a through 1.7.72.

The weakness was presented by Trương Hữu Phúc. The advisory is shared at patchstack.com. This vulnerability is known as CVE-2024-47318 since 09/24/2024. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. 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 11/01/2024).

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

Vendor

• Magazine3

Name

• PWA for WP & AMP Plugin

Version

• 1.7.0
• 1.7.1
• 1.7.2
• 1.7.3
• 1.7.4
• 1.7.5
• 1.7.6
• 1.7.7
• 1.7.8
• 1.7.9
• 1.7.10
• 1.7.11
• 1.7.12
• 1.7.13
• 1.7.14
• 1.7.15
• 1.7.16
• 1.7.17
• 1.7.18
• 1.7.19
• 1.7.20
• 1.7.21
• 1.7.22
• 1.7.23
• 1.7.24
• 1.7.25
• 1.7.26
• 1.7.27
• 1.7.28
• 1.7.29
• 1.7.30
• 1.7.31
• 1.7.32
• 1.7.33
• 1.7.34
• 1.7.35
• 1.7.36
• 1.7.37
• 1.7.38
• 1.7.39
• 1.7.40
• 1.7.41
• 1.7.42
• 1.7.43
• 1.7.44
• 1.7.45
• 1.7.46
• 1.7.47
• 1.7.48
• 1.7.49
• 1.7.50
• 1.7.51
• 1.7.52
• 1.7.53
• 1.7.54
• 1.7.55
• 1.7.56
• 1.7.57
• 1.7.58
• 1.7.59
• 1.7.60
• 1.7.61
• 1.7.62
• 1.7.63
• 1.7.64
• 1.7.65
• 1.7.66
• 1.7.67
• 1.7.68
• 1.7.69
• 1.7.70
• 1.7.71
• 1.7.72

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