LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47532: WordPress WP Crowdfunding Plugin <= 2.1.6 is vulnerable to Cross Site Scripting (XSS)

Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in Themeum WP Crowdfunding plugin <= 2.1.6 versions.

MediumCVSS 5.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This vulnerability lets an unauthenticated attacker trick a user into opening a crafted link that runs script in the victim’s browser. It affects Themeum WP Crowdfunding plugin versions up to 2.1.6. The business risk is moderate because user interaction is required, but successful exploitation can affect confidentiality, integrity, and availability at a limited level.

Executive priority

Treat this as a moderate-priority web risk. It is not listed as known exploited in the provided data, but affected public WordPress sites should be identified and remediated because XSS can support account abuse, phishing, and content tampering.

Technical view

CVE-2023-47532 is an unauthenticated reflected cross-site scripting issue in Themeum WP Crowdfunding for WordPress, reported for versions <= 2.1.6. It is mapped to CWE-79 with CVSS 3.1 score 5.8: AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:L. The provided sources do not name a fixed version or mitigation.

Likely exposure

Exposure is likely limited to WordPress sites that have the WP Crowdfunding plugin installed at version 2.1.6 or earlier. Public-facing crowdfunding or donation pages may increase the chance that users encounter attacker-supplied links.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires a victim to interact with a malicious link or request, and attack complexity is rated high in the CVSS vector.

Researcher notes

Evidence is concise and comes mainly from the CVE record and Patchstack entry. The affected range is stated as <= 2.1.6, but the provided bundle does not include proof-of-concept details, exploitation evidence, or a named fixed version.

Mitigation direction

  • Inventory WordPress sites for the WP Crowdfunding plugin.
  • Confirm whether installed versions are 2.1.6 or earlier.
  • Check Themeum, WordPress.org, or Patchstack guidance for a fixed release.
  • Update promptly if a vendor-supported fixed version is available.
  • Disable the plugin where it is not business-critical until guidance is confirmed.

Validation and detection

  • Review plugin inventories across production and staging WordPress sites.
  • Record each affected site, plugin version, and business owner.
  • Confirm whether public pages use WP Crowdfunding functionality.
  • Review web logs for unusual links or requests targeting crowdfunding pages.
  • Track remediation status until affected installations are updated or disabled.
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-47532 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
Medium
CVSS
5.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/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
5.8CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:L1.63.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.8Medium
CVSS 3.1 vector shape for CVE-2023-47532Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/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
ThemeumWP Crowdfundingwp-crowdfunding, n/aunaffected
Weakness

CWE details

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