PickPlugins Accordion Plugin up to 2.2.99 on WordPress cross site scripting

Summaryinfo

A vulnerability was found in PickPlugins Accordion Plugin up to 2.2.99 on WordPress. It has been rated as problematic. Affected is an unknown function. The manipulation leads to cross site scripting. This vulnerability is uniquely identified as CVE-2024-47342. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in PickPlugins Accordion Plugin up to 2.2.99 on WordPress. It has been rated as problematic. This issue affects an unknown function. The manipulation with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to 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. Impacted is integrity. The summary by CVE is:

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

The weakness was disclosed by Robert Devore. The advisory is shared at patchstack.com. The identification of this vulnerability is CVE-2024-47342 since 09/24/2024. The exploitation is known to be easy. The attack may be initiated remotely. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.

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

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• WordPress Plugin

Vendor

• PickPlugins

Name

• Accordion 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
• 2.2.54
• 2.2.55
• 2.2.56
• 2.2.57
• 2.2.58
• 2.2.59
• 2.2.60
• 2.2.61
• 2.2.62
• 2.2.63
• 2.2.64
• 2.2.65
• 2.2.66
• 2.2.67
• 2.2.68
• 2.2.69
• 2.2.70
• 2.2.71
• 2.2.72
• 2.2.73
• 2.2.74
• 2.2.75
• 2.2.76
• 2.2.77
• 2.2.78
• 2.2.79
• 2.2.80
• 2.2.81
• 2.2.82
• 2.2.83
• 2.2.84
• 2.2.85
• 2.2.86
• 2.2.87
• 2.2.88
• 2.2.89
• 2.2.90
• 2.2.91
• 2.2.92
• 2.2.93
• 2.2.94
• 2.2.95
• 2.2.96
• 2.2.97
• 2.2.98
• 2.2.99

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion