WPScan and the United States Government National Vulnerability Database published a notice of a vulnerability discovered in the HubSpot WordPress plugin. The vulnerability exposes users of the plugin to a Server Side Request Forgery attack.
The security researchers at WPScan published the following report:
“HubSpot < 8.8.15 – Contributor+ Blind SSRF
Description
The plugin does not validate the proxy URL given to the proxy REST endpoint, which could allow users with the edit_posts capability (by default contributor and above) to perform SSRF attacks”
This vulnerability requires that a contributor level subscriber be logged in for the exposure to happen.
The non-profit Open Web Application Security Project (OWASP), a worldwide organization dedicated to software security, an SSRF vulnerability can result in the exposure of internal services that are not meant to be exposed.
According to OWASP:
“In a Server-Side Request Forgery (SSRF) attack, the attacker can abuse functionality on the server to read or update internal resources.
The attacker can supply or modify a URL which the code running on the server will read or submit data to, and by carefully selecting the URLs, the attacker may be able to read server configuration such as AWS metadata, connect to internal services like http enabled databases or perform post requests towards internal services which are not intended to be exposed.”
The services that aren’t supposed to be exposed are:
- “Cloud server meta-data
- Database HTTP interfaces
- Internal REST interfaces
- Files – The attacker may be able to read files using <file://> URIs”
The HubSpot WordPress plugin is used by over 200,000 publishers. It provides CRM, live chat, analytics and email marketing related capabilities.
The vulnerability discovered by WPScan notes that it was fixed in version 8.8.15.
However, the changelog that documents what was updated in the software shows that the HubSpot WordPress plugin received additional updates to fix other vulnerabilities.
Here is a list of the updates according to the official changelog, in order beginning with the oldest update:
= 8.8.15 (2022-04-07) = * Fix security issue related to proxy URL = 8.9.14 (2022-04-12) = * Fix security issue related to form inputs = 8.9.20 (2022-04-13) = * Fix security issue related to sanitizing inputs
While the security firm WPScan and the National Vulnerability Database state that vulnerability was fixed in version 8.8.15, according to the HubSpot plugin changelog, there were further security fixes all the way up to version 8.9.20.
So it my be prudent to update the HubSpot plugin to at least version 8.9.20, although the absolute latest version of the HubSpot WordPress plugin, as of this writing, is version 8.11.0.
HubSpot < 8.8.15 – Contributor+ Blind SSRF
HubSpot WordPress Plugin Changelog
!function(f,b,e,v,n,t,s)
{if(f.fbq)return;n=f.fbq=function(){n.callMethod?
n.callMethod.apply(n,arguments):n.queue.push(arguments)};
if(!f._fbq)f._fbq=n;n.push=n;n.loaded=!0;n.version=’2.0′;
n.queue=[];t=b.createElement(e);t.async=!0;
t.src=v;s=b.getElementsByTagName(e)[0];
s.parentNode.insertBefore(t,s)}(window,document,’script’,
‘https://connect.facebook.net/en_US/fbevents.js’);
if( typeof sopp !== “undefined” && sopp === ‘yes’ ){
fbq(‘dataProcessingOptions’, [‘LDU’], 1, 1000);
}else{
fbq(‘dataProcessingOptions’, []);
}
fbq(‘init’, ‘1321385257908563’);
fbq(‘track’, ‘PageView’);
fbq(‘trackSingle’, ‘1321385257908563’, ‘ViewContent’, {
content_name: ‘hubspot-wordpress-plugin-vulnerability’,
content_category: ‘news wp ‘
});
So one of them is a lot of SEOs right now, and a lot of…
Here is a recap of what happened in the search forums today, through the eyes…
Navigating the world of Instagram posting involves many considerations, but one crucial aspect is timing…
I am deeply sad to report that Mark Irvine passed away unexpectedly last night. Mark…
Google AdSense has removed reference to your privacy policy as a place to withdraw consent.…
One of the big worries for Google investors was the cost of running AI to…
This website uses cookies.
Leave a Comment