CVE-2023-47232VulnerabilityPublished 21 Dec 2025

CVE-2023-47232: WP Affiliate Disclosure · Vulnerability

Affects WP Affiliate DisclosureSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
mojofywp WP Affiliate Disclosure	Affected <=1.2.6	Fixed in–

AI-suggested

European organizations should implement several targeted mitigation strategies: 1) Monitor official mojofywp and WordPress plugin repositories for updates or patches addressing CVE-2023-47232 and apply them promptly once available. 2) Restrict access to WordPress admin and plugin management interfaces using strong authentication mechanisms, including multi-factor authentication (MFA), to reduce the risk of unauthorized exploitation by authenticated users. 3) Conduct regular audits of user roles and permissions to ensure that only trusted personnel have access to plugin configuration and management features. 4) Employ web application firewalls (WAFs) with custom rules to detect and block suspicious activities targeting the plugin endpoints. 5) Implement monitoring and alerting for unusual plugin behavior or availability issues to enable rapid incident response. 6) Consider temporarily disabling or replacing the WP Affiliate Disclosure plugin if the risk of exploitation outweighs its operational necessity until a patch is released. 7) Educate staff about the risks of credential compromise and enforce strong password policies to mitigate insider threats. These measures go beyond generic advice by focusing on access control, monitoring, and proactive patch management specific to this vulnerability and plugin context.

Description

Vulnerability in mojofywp WP Affiliate Disclosure wp-affiliate-disclosure.This issue affects WP Affiliate Disclosure: from n/a through 1.2.6.

Impact

For European organizations, the primary impact of CVE-2023-47232 is potential disruption of website availability, which can affect user experience, e-commerce transactions, and brand reputation. Organizations relying on the WP Affiliate Disclosure plugin for compliance with affiliate marketing regulations may face operational challenges if the plugin becomes non-functional or unstable. Although the vulnerability does not compromise data confidentiality or integrity, availability issues can lead to downtime and loss of revenue, especially for businesses with high web traffic. The requirement for authenticated access limits the risk from external attackers but raises concerns about insider threats or compromised credentials within organizations. Given the widespread use of WordPress in Europe, particularly in countries with strong e-commerce sectors, this vulnerability could affect a significant number of websites if exploited. The absence of known exploits reduces immediate risk but does not eliminate the potential for future attacks once exploit code becomes available.

References

vdp.patchstack.com/database/wordpress/plugin/wp-affiliate-disclosure/vulnerability/wordpress-wp-affiliate-disclosure-plugin-1-2-6-broken-access-control-csrf-vulnerability?_s_id=cve (opens in a new tab)

Community reviews

Loading reviews…