Metaphor Creations Ditty sensitive data exposure in news ticker plugin
- Exploited
- No known exploitation
- Fix
- Fixed in 3.1.74
- Who is exposed
- Not reported
Summary
Ditty, a WordPress news ticker plugin from Metaphor Creations, LLC, exposes sensitive information in the data it sends out, so an attacker can retrieve embedded sensitive data. The flaw can be reached remotely over the network without logging in.
Written by a model
Original description
Insertion of Sensitive Information Into Sent Data vulnerability in Metaphor Creations, LLC Ditty ditty-news-ticker allows Retrieve Embedded Sensitive Data.This issue affects Ditty: from n/a through 3.1.73.
What to do
Upgrade to a fixed version: 3.1.74.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130625 (WordPress Ditty plugin <= 3.1.73 - Sensitive Data Exposure vulnerability), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130625 (entry last updated 2026-11-20):
Affected:
- Metaphor Creations, LLC Ditty: fixed in 3.1.74
Fixed versions: 3.1.74.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130625 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130625 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/ditty-news-ticker/vulnerability/wordpress-ditty-plugin-3-1-73-sensitive-data-exposure-vulnerability?_s_id=cve
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130625
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130625"}.Affected versions
- ditty-news-tickerfixed in 3.1.74 · through 3.1.73
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130625 |
| Record | NVD · CVE-2026-130625 |
| Other links 1 | |
| Link | patchstack.com · database/wordpress/plugin/ditty-news-ticker/vulnerability/wordpress-ditty-plugin-3-1-73-sensitive-data-exposure-vulnerability?_s_id=cve |
Questions about CVE-2026-130625
Is CVE-2026-130625 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-130625?
ditty-news-ticker: through 3.1.73 (fixed in 3.1.74).
Source: cve.now feed data
How do I fix CVE-2026-130625?
Upgrade to a fixed version: 3.1.74.
Source: cve.now feed data
Related
- CVE-2026-119493WordPress Ditty plugin <= 3.1.71 - Cross Site Scripting (XSS) vulnerability
- CVE-2026-119492WordPress Ditty plugin <= 3.1.71 - Content Injection vulnerability
- CVE-2026-80322Cross-request response leakage in PingAuthorize after asynchronous timeout and connection reuse
- CVE-2026-131266Information Disclosure through the REST API in Splunk SOAR
- CVE-2026-133084In JetBrains TeamCity before 2026.2.2, 2026.1.6 vCS root credentials could be exposed via change viewer links
- CVE-2026-132902In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 access keys of parent project AWS connections could be disclosed
No corrections so far. Something wrong on this page? Report an error.