Security readout for executives and security teams
Plain-English summary
This is a medium-severity CSRF issue in the WordPress QR Code Tag for WC plugin through version 1.9.42. If a targeted, logged-in WordPress user is tricked into an unwanted action, plugin settings may be changed. The known business impact is limited integrity loss, not data theft or outage.
Executive priority
Treat as routine but time-bound remediation for affected WordPress sites. Prioritize internet-facing commerce sites and environments where plugin settings affect customer-facing behavior, but this does not currently warrant emergency response based on supplied evidence.
Technical view
CVE-2025-32268 is CWE-352 affecting package qr-code-tag-for-wc-from-goaskle-com. CVSS 3.1 is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact, no confidentiality or availability impact. Patchstack characterizes the issue as CSRF to settings change.
Likely exposure
Exposure appears limited to WordPress sites running QR Code Tag for WC versions up to and including 1.9.42. Sites not using this plugin are not affected by the supplied sources.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. Practical abuse requires user interaction and likely depends on a logged-in user with access to relevant WordPress settings.
Researcher notes
There is a version-label inconsistency: the CVE title and affected range state through 1.9.42, while the Patchstack reference URL title mentions 1.9.35. Use the CVE affected range unless vendor guidance clarifies it.
Mitigation direction
- Inventory WordPress sites for QR Code Tag for WC and record installed versions.
- Check vendor or Patchstack guidance for a confirmed fixed version or workaround.
- Update the plugin if a fixed release is available from trusted sources.
- Disable or remove the plugin if it is unused or no fix is available.
- Restrict WordPress admin access to trusted users and managed devices.
Validation and detection
- Confirm whether qr-code-tag-for-wc-from-goaskle-com is installed on each WordPress site.
- Verify installed plugin versions against the affected range through 1.9.42.
- Review recent plugin setting changes for unexpected modifications.
- Check Patchstack and CVE records for updated fix or exploitation information.
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-32268 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
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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.
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:U/C:N/I:L/A:N2.81.4PatchstackVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
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
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.