/*! elementor-pro - v3.26.0 - 17-12-2024 */ (()=>{"use strict";class Screenshot extends elementorModules.ViewModule{getDefaultSettings(){return{empty_content_headline:"Empty Content.",crop:{width:1200,height:1500},excluded_external_css_urls:["https://kit-pro.fontawesome.com"],external_images_urls:["https://i.ytimg.com"],timeout:15e3,render_timeout:5e3,timerLabel:null,timer_label:`${ElementorScreenshotConfig.post_id} - timer`,image_placeholder:"data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=",isDebug:elementorCommonConfig.isElementorDebug,isDebugSvg:!1,...ElementorScreenshotConfig}}getDefaultElements(){const e=jQuery(ElementorScreenshotConfig.selector),t=e.find(".elementor-section-wrap > .elementor-section, .elementor > .elementor-section");return{$elementor:e,$sections:t,$firstSection:t.first(),$notElementorElements:elementorCommon.elements.$body.find("> *:not(style, link)").not(e),$head:jQuery("head")}}onInit(){return super.onInit(),this.log("Screenshot init","time"),this.timeoutTimer=setTimeout(this.screenshotFailed.bind(this),this.getSettings("timeout")),this.captureScreenshot()}captureScreenshot(){return this.elements.$elementor.length||(elementorCommon.helpers.consoleWarn("Screenshots: The content of this page is empty, the module will create a fake conent just for this screenshot."),this.createFakeContent()),this.removeUnnecessaryElements(),this.handleIFrames(),this.removeFirstSectionMargin(),this.handleLinks(),this.loadExternalCss(),this.loadExternalImages(),Promise.resolve().then(this.createImage.bind(this)).then(this.createImageElement.bind(this)).then(this.cropCanvas.bind(this)).then(this.save.bind(this)).then(this.screenshotSucceed.bind(this)).catch(this.screenshotFailed.bind(this))}createFakeContent(){this.elements.$elementor=jQuery("
The WordPress Hunk Companion Plugin<\/strong> has been recently targeted by cyber attackers<\/strong> who used a critical hole to upload insecure versions of plugins secretly. This paragon of security breach has raised eyebrows within WordPressers since it opens websites to high risks. Hackers have abused this vulnerability to inject, for example, plugins beyond those recognized properly with exploitable bugs resulting in data leakage<\/strong>, website cracking<\/strong>, or total system compromise. The specific exploit exploitation of a vulnerability allows the execution of arbitrary code and direct installation of the plugin from the WordPress.org<\/strong> repository. These risky plugins may be out of date or in other words no longer under active development, limiting their security. Such activity is counterproductive and poses a huge threat to WordPress website security<\/strong>, which can bring long-term consequences to website owners.<\/p>\n\n\n\n WordPress Hunk Companion Plugin<\/strong> was intended to boost the features of themes created by ThemeHunk. These themes are quite flexible and if you can install them, you are ready to roll, whether a small business, flying solo, or even a blogger. Though this plugin depends more on Hunk themes<\/strong>, it has become a handy tool for many WordPress users<\/strong>. At present, it is used on more than10,0000 sites. Even though it enjoys this level of popularity and is used on only about 7% of websites, it has not been immune to attackers seeking to capture any loophole that can be used to attack WordPress.<\/p>\n\n\n\n The critical CVE-2024-11972 vulnerability<\/strong> allows attackers to execute unauthenticated plugin installations<\/strong> using specially crafted POST requests. Hackers exploit this flaw to bypass administrative controls and directly install plugins with known security flaws. Discovered by WPScan researcher Daniel Rodriguez, this vulnerability impacts all versions of the WordPress Hunk Companion Plugin<\/strong> released before version 1.9.0. The latest version, which was released as a security update, addresses this critical issue and is strongly recommended for all users.<\/p>\n\n\n\n Cybercriminals<\/strong> exploiting the Hunk Companion security flaw <\/strong>have been observed installing outdated plugins like WP Query Console<\/strong>. This precise plugin has such nasty outdated flaws that a hacker can easily gain code execution (RCE)<\/strong> and more. The critical CVE-2024-11972 vulnerability<\/strong> is exploited to upload two PHP scripts to the victim sites. AThesescripts can be useful for such purposes as stealing data, modifying the contents, exploiting the loopholes, and making a persistent wrench to perform attacks in the future. This problem is a clear indication that a call for action and measures should be taken by website owners as soon as possible.<\/p>\n\n\n\n During their investigations, WPScan researchers documented active exploitation of the Hunk Companion security flaw<\/strong>. On an infected WordPress site, hackers installed risky plugins and placed malicious scripts in the root directory. These scripts enabled attackers to execute commands remotely, allowing continuous control over the compromised site. The presence of PHP droppers, which facilitate repeated unauthorized access, was particularly alarming. Similar techniques have used in other high-profile WordPress attacks, underscoring the sophistication of today\u2019s cyber threats.<\/p>\n\n\n\n The WordPress Hunk Companion Plugin<\/strong> has faced security issues in the past. An earlier vulnerability has found in version 1.8.5 and termed as CVE-2024-9707<\/strong>. A patch made available, but later, the attackers able to circumvent it and again make the sites all exposed. These recurring vulnerabilities highlight the importance of robust security practices during plugin development. Developers must implement rigorous testing and frequent updates to mitigate risks and protect users.<\/p>\n\n\n\n There are several things to note regarding the Hunk Companion security vulnerability<\/strong> To put it in context, the release of version 1.9.0 has given a new direction in dealing with the problem. The targeted plugins are reported to in continuous use, and users are encouraged to update them to prevent further abuse on their websites. <\/p>\n\n\nUnderstanding the WordPress Hunk Companion Plugin<\/strong><\/h2>\n\n\n\n
Details of the CVE-2024-11972 Vulnerability<\/strong><\/h2>\n\n\n\n
How the Security Flaw Is Being Exploited<\/strong><\/h2>\n\n\n\n
Active Exploitation Observed in the Wild<\/strong><\/h2>\n\n\n\n
A History of Security Challenges<\/strong><\/h2>\n\n\n\n
Why Updating to Version 1.9.0 Is Crucial<\/strong><\/h2>\n\n\n\n