Sassy Social Share Plugin up to 3.3.44 on WordPress cross site scripting

Summaryinfo

A vulnerability was found in Sassy Social Share Plugin up to 3.3.44 on WordPress. It has been classified as problematic. This vulnerability affects unknown code. The manipulation leads to cross site scripting. This vulnerability is referenced as CVE-2022-4451. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Sassy Social Share Plugin up to 3.3.44 on WordPress (WordPress Plugin) and classified as problematic. This issue affects an unknown code block. 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 weakness was published 12/24/2022. The advisory is shared at wordfence.com. The identification of this vulnerability is CVE-2022-4451 since 12/13/2022. 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.

Upgrading to version 3.3.45 eliminates this vulnerability.

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

Productinfo

Type

• WordPress Plugin

Name

• Sassy Social Share 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

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