dbcve.org
DittyWordPress extension · Metaphorcreations

CVE-2023-23874

MEDIUM · 5.4 CVSS v3.1 Published 2023-05-03
Fix available
A fix is available. Upgrade to 3.0.33 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Metaphor Creations Ditty plugin <= 3.0.32 versions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A stored Cross-Site Scripting (XSS) vulnerability in the Metaphor Creations Ditty WordPress plugin versions 3.0.32 and below allows authenticated users with contributor-level or higher privileges to inject malicious JavaScript code into plugin functionality. This payload persists in the database and executes when other users (including administrators) view the affected content in the WordPress dashboard or on the frontend.

MitigationUpdate Ditty plugin to version 3.0.33 or later to patch the vulnerability. As an interim measure, limit user role assignments to trusted individuals and consider using a web application firewall to filter XSS attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DittyWordPress extension
Affected:< 3.0.33

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Ditty plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Metaphorcreations Ditty' in the list. Note whether the plugin is active or inactive.
    Affected if The plugin is installed and active in WordPress
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins. Click on the Ditty plugin to view details, or check the plugin file header in wp-content/plugins/ditty/ditty.php for the 'Version' defined constant.
    Affected if The installed version is 3.0.32 or below (versions prior to 3.0.33)
  3. Identify user roles with contributor access
    In WordPress admin, go to Users > All Users and review each user's role. Contributor and higher roles (Contributor, Author, Editor, Administrator) can access plugin functionality that accepts user input.
    Affected if There are users with Contributor, Author, or Editor roles who have access to create or edit Ditty content
  4. Inspect Ditty database content for suspicious scripts
    Query the WordPress database for entries in the tables storing Ditty plugin data (typically any table with 'ditty' prefix). Look for script tags, javascript: URIs, or event handler attributes in content fields.
    Affected if Database contains unsanitized HTML or JavaScript code in Ditty-related content fields

You are affected if the Ditty plugin is installed with version 3.0.32 or below and users with contributor-level or higher privileges can access the plugin to create content that may contain injected scripts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.0.33 or later
Fixed in 3.0.33
Interim mitigation

Update Ditty plugin to version 3.0.33 or later to patch the vulnerability. As an interim measure, limit user role assignments to trusted individuals and consider using a web application firewall to filter XSS attempts.

Recommended fix High confidence

Ditty version 3.0.33

  1. Create a full backup of your WordPress site before making any changes
  2. Navigate to WordPress dashboard > Plugins > Installed Plugins
  3. Find the Ditty plugin and check for available updates
  4. Update Ditty to version 3.0.33 or later
  5. Verify the update was successfully applied by checking the plugin version number
  6. Clear any caching plugins or server-side caches if present

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ditty Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-23874 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-23874 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data