Security readout for executives and security teams
Plain-English summary
This WordPress plugin flaw can let an unauthenticated person alter a subscriber’s list status if they know that subscriber’s email address. The business risk is disruption to marketing and CRM data integrity, such as unwanted unsubscribes or subscription changes, rather than full site takeover.
Executive priority
Treat this as a moderate-priority data integrity issue for WordPress sites that rely on FluentCRM. It is unlikely to be a full infrastructure compromise, but it can disrupt customer communications, consent records, and campaign reliability.
Technical view
FluentCRM through 2.8.01 used an unsalted MD5 hash as an authorization control for subscription actions. The weakness maps to CWE-759 and is rated CVSS 3.1 6.5. Reported impact includes limited confidentiality and integrity loss, with network access, low complexity, no privileges, and no user interaction required.
Likely exposure
Internet-facing WordPress sites running FluentCRM versions up to and including 2.8.01 are the relevant exposure. Impact depends on whether attackers know target subscriber email addresses and whether the site uses FluentCRM subscription-management functions.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. A public GitHub reference exists, so defenders should assume technical details may be available, but not claim active exploitation from these sources alone.
Researcher notes
Focus validation on the authorization model for subscription-management actions and version boundaries around 2.8.01. Do not infer broader WordPress compromise from the supplied sources. Evidence is sufficient for affected-version triage but incomplete on exact exploitation prevalence.
Mitigation direction
- Upgrade FluentCRM to a version newer than 2.8.01 or the current vendor-supported release.
- Check Wordfence and vendor guidance for the fixed release and any additional recommendations.
- Review recent subscription changes for unexpected unsubscribes or list-management activity.
- Limit access to subscriber data that could reveal target email addresses.
- Back up CRM and subscriber list data before remediation where operationally appropriate.
Validation and detection
- Inventory all WordPress sites for FluentCRM installations and exact plugin versions.
- Flag any FluentCRM version up to and including 2.8.01 as vulnerable.
- Confirm the plugin was updated successfully after remediation.
- Review FluentCRM audit data or logs for unusual subscription-status changes.
- Verify marketing teams can recover wrongly changed subscriber records if needed.
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-759: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-2023-1430 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
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
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:N/S:U/C:L/I:L/A:N3.92.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/de6da87e-8f7d-4120-8a1b-390ef7733d84?source=cveCVE reference
- https://plugins.trac.wordpress.org/changeset/2899218/fluent-crm/tags/2.8.0/app/Hooks/Handlers/ExternalPages.php?old=2873074&old_path=fluent-crm%2Ftags%2F2.7.40%2Fapp%2FHooks%2FHandlers%2FExternalPages.phpCVE reference
- https://github.com/karlemilnikka/CVE-2023-1430CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=2924787%40fluent-crm&new=2924787%40fluent-crm&sfp_email=&sfph_mail=CVE reference
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.
Use of a One-Way Hash without a Salt
Use of a One-Way Hash without a Salt represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.