LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52178: WordPress WP Affiliate Disclosure Plugin <= 1.2.7 is vulnerable to Cross-Site Scripting (XSS)

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in MojofyWP WP Affiliate Disclosure allows Stored XSS.This issue affects WP Affiliate Disclosure: from n/a through 1.2.7.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-52178 is a stored cross-site scripting issue in the WordPress WP Affiliate Disclosure plugin through version 1.2.7. If exploited, malicious script could be saved and later run in another user’s browser. The source bundle does not show active exploitation or a named fixed version.

Executive priority

Treat this as a moderate WordPress application risk. It is not supported as actively exploited by the provided sources, but stored XSS can affect administrator trust, site integrity, and visitor safety. Prioritize inventory and remediation, especially on public or high-traffic sites.

Technical view

The issue is CWE-79 improper input neutralization during page generation in MojofyWP WP Affiliate Disclosure. CVSS 3.1 is 6.5: network reachable, low complexity, low privileges required, user interaction required, changed scope, and low confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress sites running the MojofyWP WP Affiliate Disclosure plugin through version 1.2.7. The provided affected data lists package name wp-affiliate-disclosure and does not identify other products or platforms.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The CVSS vector indicates exploitation requires low privileges and user interaction. Stored XSS impact depends on where the malicious content is saved and which users later view it.

Researcher notes

The bundle gives CVSS and affected range but limited remediation detail. Avoid assuming exploit availability, affected roles, or a specific fixed version. Validation should focus on confirming plugin presence, version, reachable content surfaces, and whether untrusted low-privileged users can write content rendered to others.

Mitigation direction

  • Inventory WordPress sites for WP Affiliate Disclosure installations and versions.
  • Check vendor or Patchstack guidance for a fixed release or official mitigation.
  • Update the plugin if a fixed version is available from trusted sources.
  • Restrict plugin-related content editing to trusted accounts until remediated.
  • Disable or remove the plugin where it is not required.

Validation and detection

  • Confirm whether wp-affiliate-disclosure is installed on each WordPress site.
  • Record installed plugin versions and flag versions through 1.2.7.
  • Review relevant plugin-managed content for unexpected scripts or suspicious markup.
  • Check WordPress users with plugin-related write access.
  • Monitor vendor, CVE, and Patchstack records for updated remediation details.
Prepared
Confidence
high
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-52178 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
6.5 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
MojofyWPWP Affiliate Disclosurewp-affiliate-disclosure, n/aunaffected
Weakness

CWE details

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

CWE-79 · source CWE mapping

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.