Ditty Plugin up to 3.1.42 on WordPress Setting cross site scripting

Summaryinfo

A vulnerability was found in Ditty Plugin up to 3.1.42 on WordPress. It has been classified as problematic. Affected by this issue is some unknown functionality of the component Setting Handler. Performing a manipulation results in cross site scripting. This vulnerability is reported as CVE-2024-5575. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Ditty Plugin up to 3.1.42 on WordPress. It has been classified as problematic. This affects an unknown code block of the component Setting Handler. 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. The summary by CVE is:

The Ditty WordPress plugin before 3.1.43 does not sanitise and escape some of its blocks' settings, which could allow high privilege users such as authors to perform Cross-Site Scripting attacks even when unfiltered_html is disallowed

The weakness was disclosed by Dmitrii Ignatyev. The advisory is shared at wpscan.com. This vulnerability is uniquely identified as CVE-2024-5575 since 05/31/2024. The exploitability is told to be easy. It is possible to initiate the attack 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.

Upgrading to version 3.1.43 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

• Ditty Plugin

Version

• 3.1.0
• 3.1.1
• 3.1.2
• 3.1.3
• 3.1.4
• 3.1.5
• 3.1.6
• 3.1.7
• 3.1.8
• 3.1.9
• 3.1.10
• 3.1.11
• 3.1.12
• 3.1.13
• 3.1.14
• 3.1.15
• 3.1.16
• 3.1.17
• 3.1.18
• 3.1.19
• 3.1.20
• 3.1.21
• 3.1.22
• 3.1.23
• 3.1.24
• 3.1.25
• 3.1.26
• 3.1.27
• 3.1.28
• 3.1.29
• 3.1.30
• 3.1.31
• 3.1.32
• 3.1.33
• 3.1.34
• 3.1.35
• 3.1.36
• 3.1.37
• 3.1.38
• 3.1.39
• 3.1.40
• 3.1.41
• 3.1.42

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