monastromagazine
Member
- Messages
- 11
- Reactions
- 7
Reacted by:
Thank you very much for this sir. Appreciate it.Here's the Elementor Pro v3.34.3 nulled
#### 3.34.3 - 2026-01-26
* Fix: Theme Builder WordPress view does not work as expected
* Fix: Submissions menu appears even when the setting is disabled
3.34.4 - 2026-01-29
* Fix: Shortcodes overflow the screen on Saved Templates screen in WordPress Admin
* Fix: Avoid Multiple Popups control does not work in Popups
it' s a beta versionHere's The Elementor Pro V3.35.0 NULLED
3.35.0 - 2026-02-02
* Tweak: Extended the color picker to support ACF fields - Editor V4
* Tweak: Enabled size variables with custom units across relevant controls - Editor V4
* Tweak: Enabled size variables in border radius controls - Editor V4
3.35.1 - 2026-02-11
* Fix: Enqueue script errors when `WP_DEBUG` is enabled ([#34617](https://github.com/elementor/elementor/issues/34617))
* Fix: General UI issues in Editor screens in WordPress Admin
This isn't a compromised file necessarily. The code builds a fake license payload, writes it straight into the WP options, and adds a pre_http_request filter that intercepts calls to my.elementor.com and always returns a 200 with the fake valid response - ALSO KNOWN AS NULLING.Nobody checks plugins anymore, people uploading compromised plugins with backdoors.
It fetch JSON from wordpressnull.org. Hostinger flaged /elementor-pro/elementor-pro.php like compromised file.
$_config = (object) [
"name" => "elementor",
"pro" => "_pro_",
"wpn" => "wordpressnull", <-------
"timeout" => strtotime('+12 hours', current_time('timestamp'))
];
Without @raz0r safe nulled versions not exist in internet anymore. Not trust ANYONE
In the past, we couldn’t access the template library, and everything worked fine. Who decided that it’s necessary to compromise our websites by relying on unknown external sources?This isn't a compromised file necessarily. The code builds a fake license payload, writes it straight into the WP options, and adds a pre_http_request filter that intercepts calls to my.elementor.com and always returns a 200 with the fake valid response - ALSO KNOWN AS NULLING.
What you see with wordpressnull.org is that it uses that proxy to download PRO templates. Otherwise it wouldn't be possible to fetch them from the Elementor cloud server without a legitimate license.
I'm not claiming this is the SAFEST way to do it but you can check older versions by raz0r and you will see the files use the same NULL method as this one. https://nullcave.club/resources/elementor-pro-wordpress-page-builder-premium.14/history
So this isn't much different or more dangerous than what raz0r posted.
I don't know, I guess it's more cool and closer to proper behavior.In the past, we couldn’t access the template library, and everything worked fine. Who decided that it’s necessary to compromise our websites by relying on unknown external sources?
} elseif (strpos($url, "{$_config->api}/connect/v1/library/get_template_content") !== false) {
$response = wp_remote_get("{$_config->templates}/{$parsed_args['body']['id']}.json", ['sslverify' => false, 'timeout' => 25]);
if (wp_remote_retrieve_response_code($response) == 200) {
return $response;
} else {
return $pre;
}