dbcve.org
Animated Number CountersWordPress extension · Wpmart

CVE-2023-24393

MEDIUM · 5.4 CVSS v3.1 Published 2023-08-10
Fix available
A fix is available. Upgrade to after 1.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
Auth. (editor+) Stored Cross-Site Scripting (XSS) vulnerability in Sk. Abul Hasan Animated Number Counters plugin <= 1.6 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 · moderate confidence

Authenticated (editor+) Stored Cross-Site Scripting (XSS) vulnerability in the Sk. Abul Hasan Animated Number Counters WordPress plugin versions 1.6 and below. An attacker with editor-level or higher privileges can inject malicious JavaScript code that gets stored in the database and executed when other users view the affected pages.

MitigationUpdate the Animated Number Counters plugin to version 1.7 or later which includes proper input sanitization and output encoding to prevent XSS attacks.

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
Animated Number CountersWordPress extension
Affected:<= 1.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 Animated Number Counters plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for a folder containing 'animated-number-counters' or similar naming. Locate the main plugin PHP file and inspect the plugin header for the Version field.
    Affected if The plugin is installed and the Version listed is 1.6 or lower
  2. Confirm the plugin is active
    In WordPress admin under Plugins > Instored Plugins, verify the Animated Number Counters plugin has an 'Active' status under the plugin name.
    Affected if The plugin is currently active on the WordPress site
  3. Inspect plugin database options for malicious scripts
    Query the wp_options table (or options table with appropriate prefix) for options containing the plugin name. Look for any option values containing script tags, iframe tags, or javascript: URIs. Common option names may include 'abhnc_settings', 'animated_number_counter_options', or similar. Use: SELECT * FROM wp_options WHERE option_value LIKE '%<script%' OR option_value LIKE '%javascript:%';
    Affected if Any option values stored by the plugin contain HTML script tags, event handlers, or javascript: protocol links that could execute as XSS
  4. Review page content where the plugin shortcode is deployed
    Identify pages or posts using the plugin shortcode (commonly [animated_counter] or similar). View the page source in a browser and manually inspect for any injected script tags within the counter display area that were not intentionally added by an administrator.
    Affected if Unexpected script tags or malicious attributes appear in the HTML output of pages using the plugin shortcode

You are affected if the Animated Number Counters plugin versions 1.6 or below is installed and active, and either suspicious script tags are found in the plugin options database or in the rendered output of pages using the plugin.

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.

From vendor data
Upgrade available Upgrade to a release after 1.6
Interim mitigation

Update the Animated Number Counters plugin to version 1.7 or later which includes proper input sanitization and output encoding to prevent XSS attacks.

Fix this in Animated Number Counters Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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