dbcve.org
Thanh Toan Quet Ma Qr Code Tu DongWordPress extension · WordPress

CVE-2024-8914

HIGH · 7.2 CVSS v3.1 Published 2024-09-25
Fix available
A fix is available. Upgrade to after 2.0.1 or later.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
The Thanh Toán Quét Mã QR Code Tự Động – MoMo, ViettelPay, VNPay và 40 ngân hàng Việt Nam plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 2.0.1 due to incorrect use of the wp_kses_allowed_html function, which allows the 'onclick' attribute for certain HTML elements without sufficient restriction or context validation. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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

The Thanh Toán QR Code payment plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to 2.0.1 due to incorrect use of wp_kses_allowed_html that permits the dangerous 'onclick' attribute without proper validation. Unauthenticated attackers can inject malicious scripts that execute whenever users access injected pages.

MitigationUpdate the plugin to version 2.0.2 or later which should properly restrict or remove the 'onclick' attribute from allowed HTML, and audit existing content for any injected XSS payloads.

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
Thanh Toan Quet Ma Qr Code Tu DongWordPress extension
Affected:<= 2.0.1

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
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 the plugin is installed
    Navigate to WordPress admin > Plugins and confirm 'Thanh Toan Quet Ma Qr Code Tu Dong' appears in the installed plugins list, or inspect the /wp-content/plugins/ directory for a folder containing 'thanh-toan' or 'qr-code' in the name
    Affected if The plugin appears in the installed plugins list or filesystem
  2. Check the installed plugin version
    In WordPress admin, click on the plugin to view its details and note the version number, or open the main plugin PHP file and look for the 'Version:' header comment in the plugin file header
    Affected if The reported version is 2.0.1 or lower
  3. Inspect stored content for injected onclick attributes
    Search the WordPress database (wp_posts table) or use a plugin like WP-Optimize to search post content for strings containing 'onclick=' across all post types, especially pages containing QR code payment functionality
    Affected if Any posts, pages, or custom post types contain 'onclick=' attribute values that were not intentionally added by an administrator
  4. Check for unauthorized script injections in QR code payment forms
    View the frontend of any page where the QR code payment shortcode or widget is deployed, then view the page source and search for unexpected inline onclick handlers or script tags that were not authored by administrators
    Affected if Unexpected JavaScript event handlers or script tags appear in the HTML output of pages using the plugin's QR code payment feature

You are affected if the Thanh Toan QR Code plugin is installed at version 2.0.1 or lower and any stored content contains unauthorized onclick attributes or 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 a release after 2.0.1
Interim mitigation

Update the plugin to version 2.0.2 or later which should properly restrict or remove the 'onclick' attribute from allowed HTML, and audit existing content for any injected XSS payloads.

Recommended fix Moderate confidence

Latest version > 2.0.1 (check WordPress plugin repository for current stable release)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Thanh Toán Quét Mã QR Code Tự Động – MoMo, ViettelPay, VNPay và 40 ngân hàng Việt Nam' plugin
  4. Check the current installed version to confirm it is 2.0.1 or below
  5. Update the plugin to the latest available version from the WordPress plugin repository

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

Fix this in Thanh Toan Quet Ma Qr Code Tu Dong Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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