Security readout for executives and security teams
Plain-English summary
CVE-2025-46506 affects the WordPress WpZon Amazon Affiliate Plugin through version 1.3. A malicious site or link could abuse CSRF behavior to cause reflected cross-site scripting when a victim interacts with it. The sources do not identify active exploitation or a confirmed fixed version.
Executive priority
Treat this as a high-priority WordPress plugin exposure, especially on revenue-generating affiliate sites. It is not confirmed as actively exploited, but the combination of public web exposure, no privileges required, and XSS impact makes prompt inventory and mitigation appropriate.
Technical view
The CVE describes CWE-352 CSRF in Lora77 wpzon that can lead to reflected XSS. CVSS 3.1 is 7.1, network-exploitable with low attack complexity, no privileges required, user interaction required, and changed scope with low confidentiality, integrity, and availability impact.
Likely exposure
Internet-facing WordPress sites using WpZon Amazon Affiliate Plugin version 1.3 or earlier are the relevant exposure. Sites without this plugin, or on versions not covered by the CVE record, are not shown as affected by the provided sources.
Exploitation context
CISA KEV is false in the bundle, and no provided source confirms exploitation in the wild. Practical abuse requires user interaction, likely through a crafted request or link, and the impact is reflected XSS rather than direct server compromise.
Researcher notes
Evidence is limited to the CVE record and Patchstack listing. The bundle names affected versions through 1.3, CVSS 7.1, CWE-352, and reflected XSS impact. It does not provide a patched version, proof of exploitation, or detailed vulnerable endpoint information.
Mitigation direction
- Inventory all WordPress sites for the wpzon plugin and installed version.
- Check vendor and Patchstack guidance for a fixed release or official mitigation.
- Disable or remove WpZon where it is not business-critical.
- Prioritize remediation for administrator-facing or high-traffic WordPress sites.
- Use existing WordPress security controls to reduce CSRF and XSS impact.
Validation and detection
- Confirm whether WpZon Amazon Affiliate Plugin is installed on each WordPress site.
- Record exact plugin versions and flag version 1.3 or earlier.
- Review Patchstack and CVE records for updated fix information.
- Check security logs for suspicious wpzon-related requests or unusual administrator browser activity.
- Validate that remediation did not break affiliate content workflows.
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-352: 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-2025-46506 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
- High
- CVSS
- 7.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:L
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.
SSVC decision data
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:L2.83.7PatchstackVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/Wordpress/Plugin/wpzon/vulnerability/wordpress-wpzon-amazon-affiliate-plugin-plugin-1-3-csrf-to-xss-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
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.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.