LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47521: WordPress Q2W3 Post Order Plugin <= 1.2.8 is vulnerable to Cross Site Scripting (XSS)

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Max Bond, AndreSC Q2W3 Post Order allows Reflected XSS.This issue affects Q2W3 Post Order: from n/a through 1.2.8.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a reflected cross-site scripting issue in the WordPress Q2W3 Post Order plugin through version 1.2.8. An attacker would need a user to interact with a crafted request or link. Successful exploitation could run script in the victim’s browser, creating limited confidentiality, integrity, and availability impact.

Executive priority

Treat as a high-priority WordPress hygiene issue, especially for public sites using this plugin. Prioritize confirmation of exposure and remediation, but avoid emergency framing unless internal evidence or new public sources show exploitation.

Technical view

CVE-2023-47521 is CWE-79 in Max Bond, AndreSC Q2W3 Post Order for WordPress. The CVSS 3.1 score is 7.1 with network attack vector, low complexity, no privileges required, and required user interaction. Scope is changed, with low C/I/A impact. Sources identify reflected XSS through version 1.2.8.

Likely exposure

Exposure is limited to WordPress sites with Q2W3 Post Order installed at version 1.2.8 or earlier. The bundle does not identify affected CPEs, install counts, or a fixed version.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. The CVSS vector indicates remote reachability but requires victim interaction, consistent with reflected XSS rather than direct unauthenticated takeover.

Researcher notes

Evidence is sparse in the supplied bundle. The key facts are reflected XSS, affected through 1.2.8, CVSS 7.1, CWE-79, and no KEV flag. The bundle does not provide vulnerable parameters, proof-of-concept details, or fixed-version data.

Mitigation direction

  • Inventory WordPress sites for Q2W3 Post Order installations.
  • Confirm whether installed versions are 1.2.8 or earlier.
  • Check vendor, WordPress plugin, or Patchstack guidance for a fixed release.
  • Update if a fixed release is available from a trusted source.
  • Disable or remove the plugin if it is unnecessary or cannot be remediated.

Validation and detection

  • Review WordPress plugin inventory for package name q2w3-post-order.
  • Record exact installed plugin version on each WordPress site.
  • Check Patchstack and CVE records for updated remediation details.
  • Review web logs for suspicious requests targeting plugin-related pages or parameters.
  • Confirm compensating controls do not rely on unverified exploit assumptions.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
cve · low confidence lookup

CVE-2023-47521 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2023-47521Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Max Bond, AndreSCQ2W3 Post Orderq2w3-post-order, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.