Cross-Site Scripting
4 records100%First: 2022. Latest: 2024.
Plugin security history
The Wordfence Intelligence dataset currently contains 4 vulnerability records associated with Vietnam Checkout for WooCommerce, published between 2022 and 2024.
Dataset last synchronized: 2026-08-03 00:31:25 UTC
At a glance
| Year | Records | Relative volume |
|---|---|---|
| 2022 | 1 | |
| 2023 | 1 | |
| 2024 | 2 |
| Severity | Records | Share |
|---|---|---|
| High | 1 | 25% |
| Medium | 3 | 75% |
First: 2022. Latest: 2024.
Patch status reflects the latest successfully synchronized source dataset and must be checked against the installed version.
2.0.82.0.62.0.5Ranges are deduplicated by source range record and shown with the associated disclosure and known patched versions.
| Affected range | Vulnerability | Published | Patched version | Severity |
|---|---|---|---|---|
*-2.0.7 | Woocommerce Vietnam Checkout <= 2.0.7 - Authenticated (Shop manager+) Stored Cross-Site Scripting | February 5, 2024 | 2.0.8 | Medium |
*-2.0.7 | Woocommerce Vietnam Checkout <= 2.0.8 - Authenticated (Admin+) Stored Cross-Site Scripting | January 10, 2024 | 2.0.8 | Medium |
*-2.0.5 | Woocommerce Vietnam Checkout <= 2.0.5 - Unauthenticated Stored Cross-Site Scripting | November 6, 2023 | 2.0.6 | High |
*-2.0.4 | Woocommerce Vietnam Checkout <= 2.0.4 - Reflected Cross-Site Scripting | December 9, 2022 | 2.0.5 | Medium |
Selected source records
Published: February 5, 2024
Published: January 10, 2024
Published: November 6, 2023
Published: December 9, 2022
Published: November 6, 2023
Published: December 9, 2022
Published: February 5, 2024
Published: January 10, 2024
Running an affected version does not prove that a website was compromised. Suspicious redirects, unknown administrators, injected content, unexpected files or recurring malware may require a manual investigation.
Vulnerability data: Wordfence Intelligence. Analysis and practical guidance: 3Zero Digital.
This page aggregates active Production Feed records. Counts are not software-quality rankings, and an affected version does not prove exploitation or infection. Read the full methodology.