CVE-2024-34550: Dynamics 365 Integration (WordPress plugin) · Sensitive Data in Logs
Affects Dynamics 365 Integration (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 5.3 Medium · patch available : update Dynamics 365 Integration (WordPress plugin) when convenient.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 9 May 2024
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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AlexaCRM Dynamics 365 Integration | Affected
| Fixed in– |
AI-suggested
A patch is available for this vulnerability. Since the product is a cloud service, the vendor typically manages remediation server-side. Users should verify with the vendor advisory for confirmation of patch deployment and ensure their integration is updated to a version beyond 1.3.17 or that the vendor has applied the fix. No additional mitigation steps are indicated by the vendor at this time.
Description
Insertion of Sensitive Information into Log File vulnerability in AlexaCRM Dynamics 365 Integration.This issue affects Dynamics 365 Integration: from n/a through 1.3.17.