Dylan James Zephyr Project Manager Plugin up to 3.3.97 on WordPress privileges management

Summaryinfo

A vulnerability identified as critical has been detected in Dylan James Zephyr Project Manager Plugin up to 3.3.97 on WordPress. This affects an unknown function. This manipulation causes privileges management. This vulnerability is registered as CVE-2024-37484. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability classified as critical was found in Dylan James Zephyr Project Manager Plugin up to 3.3.97 on WordPress. Affected by this vulnerability is some unknown functionality. The manipulation with an unknown input leads to a privileges management vulnerability. The CWE definition for the vulnerability is CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Improper Privilege Management vulnerability in Dylan James Zephyr Project Manager allows Privilege Escalation.This issue affects Zephyr Project Manager: from n/a through 3.3.97.

The weakness was published by Shaman0x01. The advisory is shared at patchstack.com. This vulnerability is known as CVE-2024-37484 since 06/09/2024. The exploitation appears to be easy. The attack can be launched remotely. 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 07/09/2024). MITRE ATT&CK project uses the attack technique T1068 for this issue.

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

• Project Management Software

Vendor

• Dylan James

Name

• Zephyr Project Manager Plugin

Version

• 3.3.0
• 3.3.1
• 3.3.2
• 3.3.3
• 3.3.4
• 3.3.5
• 3.3.6
• 3.3.7
• 3.3.8
• 3.3.9
• 3.3.10
• 3.3.11
• 3.3.12
• 3.3.13
• 3.3.14
• 3.3.15
• 3.3.16
• 3.3.17
• 3.3.18
• 3.3.19
• 3.3.20
• 3.3.21
• 3.3.22
• 3.3.23
• 3.3.24
• 3.3.25
• 3.3.26
• 3.3.27
• 3.3.28
• 3.3.29
• 3.3.30
• 3.3.31
• 3.3.32
• 3.3.33
• 3.3.34
• 3.3.35
• 3.3.36
• 3.3.37
• 3.3.38
• 3.3.39
• 3.3.40
• 3.3.41
• 3.3.42
• 3.3.43
• 3.3.44
• 3.3.45
• 3.3.46
• 3.3.47
• 3.3.48
• 3.3.49
• 3.3.50
• 3.3.51
• 3.3.52
• 3.3.53
• 3.3.54
• 3.3.55
• 3.3.56
• 3.3.57
• 3.3.58
• 3.3.59
• 3.3.60
• 3.3.61
• 3.3.62
• 3.3.63
• 3.3.64
• 3.3.65
• 3.3.66
• 3.3.67
• 3.3.68
• 3.3.69
• 3.3.70
• 3.3.71
• 3.3.72
• 3.3.73
• 3.3.74
• 3.3.75
• 3.3.76
• 3.3.77
• 3.3.78
• 3.3.79
• 3.3.80
• 3.3.81
• 3.3.82
• 3.3.83
• 3.3.84
• 3.3.85
• 3.3.86
• 3.3.87
• 3.3.88
• 3.3.89
• 3.3.90
• 3.3.91
• 3.3.92
• 3.3.93
• 3.3.94
• 3.3.95
• 3.3.96
• 3.3.97

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