Fix origin / domain terminology (#1688)
This commit is contained in:
@@ -14,7 +14,7 @@ beef:
|
||||
Afterwards, the URI to trigger is: http://vulnerable-wordpress.site/wp-content/plugins/beefbind/beefbind.php,
|
||||
and the command to execute can be send by a POST-parameter named 'cmd', with a 'BEEF' header containing the value of the auth_key option.
|
||||
However, there are more stealthy ways to send the POST request to execute the command, depending on the target.
|
||||
CORS headers have been added to allow bidirectional crossdomain communication.
|
||||
CORS headers have been added to allow bidirectional crossorigin communication.
|
||||
authors: ['Bart Leppens', 'Erwan LR']
|
||||
target:
|
||||
working: ['ALL']
|
||||
|
||||
@@ -9,7 +9,7 @@ beef:
|
||||
enable: true
|
||||
category: "Misc"
|
||||
name: "Wordpress Post-Auth RCE"
|
||||
description: "This module attempts to upload and activate a malicious wordpress plugin. Afterwards, the URI to trigger it is: http://vulnerable-wordpress.site/wordpress/wp-content/plugins/beefbind/beefbind.php. The command to execute can be send by a POST-parameter named 'cmd'. CORS headers have been added to allow bidirectional crossdomain communication."
|
||||
description: "This module attempts to upload and activate a malicious wordpress plugin. Afterwards, the URI to trigger it is: http://vulnerable-wordpress.site/wordpress/wp-content/plugins/beefbind/beefbind.php. The command to execute can be send by a POST-parameter named 'cmd'. CORS headers have been added to allow bidirectional crossorigin communication."
|
||||
authors: ["Bart Leppens"]
|
||||
target:
|
||||
working: ["ALL"]
|
||||
|
||||
Reference in New Issue
Block a user