dbcve.org
Typing TextWordPress extension · Wpdeveloper

CVE-2024-5058

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-21
Fix available
A fix is available. Upgrade to 1.2.6 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
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in WPDeveloper Typing Text allows Stored XSS.This issue affects Typing Text: from n/a through 1.2.5.

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 · moderate confidence

Stored XSS vulnerability in the WPDeveloper Typing Text WordPress plugin allows unauthenticated attackers to inject malicious JavaScript via plugin settings that gets stored in the database and executed when users view pages displaying the typing text effect.

MitigationUpdate to a patched version of the Typing Text plugin when available; until then, restrict editor access and audit existing content for malicious script injections.

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
Typing TextWordPress extension
Affected:< 1.2.6

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 Typing Text plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Typing Text' or 'Typing Text by WPDeveloper'. Alternatively, check the /wp-content/plugins/ directory for a folder named 'typing-text' or similar.
    Affected if The plugin is installed and present in the WordPress environment
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Typing Text and look at the version number displayed. Compare it to the affected range: versions below 1.2.6 are vulnerable.
    Affected if The installed version is lower than 1.2.6
  3. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify the Typing Text plugin has the 'Active' status indicator, or check the wp_options table for an active_plugins entry containing 'typing-text'.
    Affected if The plugin is active and processing user content
  4. Inspect plugin settings for suspicious script injections
    Navigate to the plugin settings page (usually under Settings > Typing Text or a dedicated WPDeveloper menu). Examine any text fields where typing text content is configured. Check for script tags, javascript: URIs, or encoded payloads in the saved values.
    Affected if Plugin settings contain unsanitized script tags or javascript: handlers
  5. Check database for stored XSS payloads in typing text records
    Query the wp_postmeta or wp_options table for entries related to typing text that contain suspicious patterns: <script, javascript:, onload=, onerror=, or encoded characters like &#x. Use: SELECT * FROM wp_postmeta WHERE meta_value LIKE '%<script%' OR meta_value LIKE '%javascript:%'.
    Affected if Database records contain malicious script injections stored by the plugin

The environment is affected if the Typing Text plugin version is below 1.2.6, the plugin is active, and the plugin settings or database contain unsanitized JavaScript that could be executed when pages with the typing effect are viewed.

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 1.2.6 or later
Fixed in 1.2.6
Interim mitigation

Update to a patched version of the Typing Text plugin when available; until then, restrict editor access and audit existing content for malicious script injections.

Recommended fix High confidence

Typing Text version 1.2.6

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Typing Text' plugin in the list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.2.6
  5. 5. Alternatively, navigate to Dashboard > Updates and select the Typing Text plugin for update
  6. 6. After updating, verify the plugin version shows 1.2.6

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

Fix this in Typing Text Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5058 — 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-2024-5058 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