AyeCode GeoDirectory Plugin up to 2.3.80 on WordPress cross site scripting

Summaryinfo

A vulnerability described as problematic has been identified in AyeCode GeoDirectory Plugin up to 2.3.80 on WordPress. Affected by this vulnerability is an unknown functionality. The manipulation results in cross site scripting. This vulnerability is cataloged as CVE-2024-50437. The attack may be launched remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in AyeCode GeoDirectory Plugin up to 2.3.80 on WordPress. It has been classified as problematic. Affected is an unknown code block. The manipulation with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity. CVE summarizes:

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Paolo GeoDirectory geodirectory allows Stored XSS.This issue affects GeoDirectory: from n/a through <= 2.3.80.

The weakness was shared by João Pedro Soares De Alcântara. The advisory is shared for download at patchstack.com. This vulnerability is traded as CVE-2024-50437 since 10/24/2024. The exploitability is told to be easy. It is possible to launch the attack remotely. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1059.007.

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

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• WordPress Plugin

Vendor

• AyeCode

Name

• GeoDirectory Plugin

Version

• 2.3.0
• 2.3.1
• 2.3.2
• 2.3.3
• 2.3.4
• 2.3.5
• 2.3.6
• 2.3.7
• 2.3.8
• 2.3.9
• 2.3.10
• 2.3.11
• 2.3.12
• 2.3.13
• 2.3.14
• 2.3.15
• 2.3.16
• 2.3.17
• 2.3.18
• 2.3.19
• 2.3.20
• 2.3.21
• 2.3.22
• 2.3.23
• 2.3.24
• 2.3.25
• 2.3.26
• 2.3.27
• 2.3.28
• 2.3.29
• 2.3.30
• 2.3.31
• 2.3.32
• 2.3.33
• 2.3.34
• 2.3.35
• 2.3.36
• 2.3.37
• 2.3.38
• 2.3.39
• 2.3.40
• 2.3.41
• 2.3.42
• 2.3.43
• 2.3.44
• 2.3.45
• 2.3.46
• 2.3.47
• 2.3.48
• 2.3.49
• 2.3.50
• 2.3.51
• 2.3.52
• 2.3.53
• 2.3.54
• 2.3.55
• 2.3.56
• 2.3.57
• 2.3.58
• 2.3.59
• 2.3.60
• 2.3.61
• 2.3.62
• 2.3.63
• 2.3.64
• 2.3.65
• 2.3.66
• 2.3.67
• 2.3.68
• 2.3.69
• 2.3.70
• 2.3.71
• 2.3.72
• 2.3.73
• 2.3.74
• 2.3.75
• 2.3.76
• 2.3.77
• 2.3.78
• 2.3.79
• 2.3.80

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion