HomeWordPress vulnerabilitiesDitty
Ditty vulnerabilities
Ditty has 12 known vulnerabilities in this database. The most recent published record is dated 21 Sep 2026.
- Known vulnerabilities
- 12
- Active installs
- 30,000+
- Latest version
- 3.1.71
- Last updated
- 23 Sep 2026
- Most recent
- 21 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-93339 | Medium 5.1 | Before 3.1.70 | Fixed in 3.1.70 | 21 Sep 2026 |
| Broken access control CVE-2026-9011 | High 7.5 | Up to 3.1.65 | Fixed in a later version (latest 3.1.71) | 22 May 2026 |
| Server-side request forgery (SSRF) CVE-2025-8085 | High 8.6 | Before 3.1.58 | Fixed in 3.1.58 | 8 Sep 2025 |
| Cross-site scripting (XSS) CVE-2024-13357 | Medium 4.8 | Before 3.1.52 | Fixed in 3.1.52 | 15 May 2025 |
| Cross-site scripting (XSS) CVE-2024-9600 | Medium 4.8 | Before 3.1.47 | Fixed in 3.1.47 | 21 Nov 2024 |
| Security weakness CVE-2024-6715 | Medium 6.1 | Before 3.1.46 | Fixed in 3.1.46 | 23 Aug 2024 |
| Cross-site scripting (XSS) CVE-2024-6710 | Medium 5.4 | Before 3.1.46 | Fixed in 3.1.46 | 5 Aug 2024 |
| Cross-site scripting (XSS) CVE-2024-5575 | Medium 4.7 | Before 3.1.43 | Fixed in 3.1.43 | 13 Jul 2024 |
| Cross-site scripting (XSS) CVE-2024-3939 | Medium 5.4 | Before 3.1.36 | Fixed in 3.1.36 | 27 May 2024 |
| PHP object injection CVE-2024-3954 | High 8.8 | Not yet published | Check for an update | 14 May 2024 |
| Cross-site scripting (XSS) CVE-2023-4148 | Medium 6.1 | Before 3.1.25 | Fixed in 3.1.25 | 25 Sep 2023 |
| Cross-site scripting (XSS) CVE-2022-0533 | Medium 6.1 | Before 3.0.15 | Fixed in 3.0.15 | 7 Mar 2022 |
Read the published descriptions
- CVE-2026-93339, 21 Sep 2026
- Metaphor Creations Ditty (ditty-news-ticker) before 3.1.70 contains a stored cross-site scripting vulnerability that allows authenticated users with Author-level privileges or higher to inject arbitrary HTML elements by supplying malicious wrapper attribute values in layout tags. The ditty_layout_render_tag_wrapper() function inserts caller-supplied wrapper attribute values directly as HTML element names without allowlist validation, bypassing wp_kses_post() sanitization because KSES runs at save time before layout tag attributes are resolved at render time, causing the payload to execute in the browser of any visitor viewing posts or pages embedding the affected Ditty item. CVE record
- CVE-2026-9011, 22 May 2026
- The Ditty - Responsive News Tickers, Sliders, and Lists plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 3.1.65. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to retrieve the full item content of non-public Dittys - including drafts, pending, scheduled, and disabled entries - by enumerating integer post IDs against the ditty_init AJAX endpoint. Unlike the non-AJAX init() counterpart, init_ajax() does not verify that the requested Ditty has a 'publish' post status before loading and returning its items, allowing content that administrators explicitly withheld from public view to be extracted. CVE record
- CVE-2025-8085, 8 Sep 2025
- The Ditty WordPress plugin before 3.1.58 lacks authorization and authentication for requests to its displayItems endpoint, allowing unauthenticated visitors to make requests to arbitrary URLs. CVE record
- CVE-2024-13357, 15 May 2025
- The Ditty WordPress plugin before 3.1.52 does not sanitise and escape some of its settings, which could allow high privilege users such as author to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup). CVE record
- CVE-2024-9600, 21 Nov 2024
- The Ditty WordPress plugin before 3.1.47 does not sanitise and escape some of its settings, which could allow high privilege users such as author to perform Stored Cross-Site Scripting attacks. CVE record
- CVE-2024-6715, 23 Aug 2024
- The Ditty WordPress plugin before 3.1.46 re-introduced a previously fixed security issue (https://wpscan.com/vulnerability/80a9eb3a-2cb1-4844-9004-ba2554b2d46c/) in v3.1.39 CVE record
- CVE-2024-6710, 5 Aug 2024
- The Ditty WordPress plugin before 3.1.45 does not sanitise and escape some parameters, which could allow users with a role as low as Contributor to perform Cross-Site Scripting attacks. CVE record
- CVE-2024-5575, 13 Jul 2024
- 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 CVE record
- CVE-2024-3939, 27 May 2024
- The Ditty WordPress plugin before 3.1.36 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup) CVE record
- CVE-2024-3954, 14 May 2024
- The Ditty plugin for WordPress is vulnerable to PHP Object Injection in all versions up to 3.1.38 via deserialization of untrusted input when adding a new ditty. This makes it possible for authenticated attackers, with contributor-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable plugin. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code. CVE record
- CVE-2023-4148, 25 Sep 2023
- The Ditty WordPress plugin before 3.1.25 does not sanitise and escape some parameters and generated URLs before outputting them back in attributes, leading to Reflected Cross-Site Scripting which could be used against high privilege users such as admin. CVE record
- CVE-2022-0533, 7 Mar 2022
- The Ditty (formerly Ditty News Ticker) WordPress plugin before 3.0.15 is affected by a Reflected Cross-Site Scripting (XSS) vulnerability. CVE record
What to do if you run Ditty
If you run Ditty, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Ditty vulnerabilities
Free. We email you when a new vulnerability is published for Ditty, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.