Dynamics 365 Integration <= 1.3.12 - Cross-Site Request Forgery via wp_ajax_wpcrm_log

2023-03-13 00:00
Anonymous

Strategic Overview

Status
Patched in 1.3.13
Affected Plugin
Dynamics 365 Integration
Affected Version
<= 1.3.12
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all Dynamics 365 Integration vulnerabilities

At a glance

This record tracks a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Dynamics 365 Integration WordPress plugin, affecting versions <= 1.3.12. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.3.13; sites on affected versions should update now. Disclosed March 2023.

Vulnerability Overview

The Dynamics 365 Integration plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.3.12. This is due to missing or incorrect nonce validation on 'wp_ajax_wpcrm_log' AJAX action. This makes it possible for unauthenticated attackers to trigger the download of log files via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Dynamics 365 Integration <= 1.3.12 carries this weakness at wp_ajax_wpcrm_log, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Dynamics 365 Integration the fix is 1.3.13: builds <= 1.3.12 are affected, anything from 1.3.13 onward is not.

Remediation

Update to version 1.3.13, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Dynamics 365 Integration: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Dynamics 365 Integration 1.3.13 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/7945110e-2a9d-4e0e-b0e8-77c16694993b

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C