Security readout for executives and security teams
Plain-English summary
This vulnerability affects a WordPress WooCommerce payment gateway plugin and can let an attacker make a user’s browser run unwanted script. It is not listed as actively exploited in KEV. Business urgency is moderate for sites still running version 1.0, especially payment-related WordPress sites.
Executive priority
Treat this as a moderate-priority cleanup item. It is payment-site adjacent and unauthenticated, but requires user interaction and has no provided evidence of active exploitation. Prioritize internet-facing WordPress commerce sites first.
Technical view
CVE-2021-39309 is a reflected cross-site scripting issue in Parsian Bank Gateway for Woocommerce up to version 1.0. The source attributes it to unsafe debugging output of POST variables in vendor/dpsoft/parsian-payment/sample/rollback-payment.php. CVSS 3.1 is 6.1, CWE-79, network reachable, no privileges required, user interaction required.
Likely exposure
Exposure is likely limited to WordPress/WooCommerce sites with Parsian Bank Gateway for Woocommerce version 1.0 installed, particularly if the bundled sample rollback-payment.php file is reachable from the web.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation evidence. Exploitation requires user interaction, consistent with reflected XSS. The provided sources do not name a fixed version or vendor patch.
Researcher notes
Focus on confirming plugin version, file presence, and route reachability. The evidence identifies unsafe POST variable output in a sample rollback handler, but does not provide a fixed release. Avoid assuming broader Parsian Bank products are affected beyond this WooCommerce plugin entry.
Mitigation direction
- Inventory WordPress sites for Parsian Bank Gateway for Woocommerce version 1.0.
- Check Wordfence or vendor guidance for a patched or maintained replacement.
- Disable or remove the plugin where it is not business-critical.
- Restrict public access to exposed sample or vendor files where operationally safe.
- Use compensating controls such as WAF rules for suspicious rollback-payment.php requests.
Validation and detection
- Confirm installed plugin name and version from WordPress administration or asset inventory.
- Verify whether vendor/dpsoft/parsian-payment/sample/rollback-payment.php exists in deployed copies.
- Review web logs for requests to rollback-payment.php and related plugin paths.
- Confirm no trusted payment workflows depend on the vulnerable sample file.
- Document findings and remediation status for each affected WordPress site.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-39309 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.1MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/vulnerability-advisories/#CVE-2021-39309CVE reference · x_refsource_MISC
- https://plugins.trac.wordpress.org/browser/parsian-bank-gateway-for-woocommerce/tags/1.0/vendor/dpsoft/parsian-payment/sample/rollback-payment.php#L39CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.