Metasploit-framework: Meterpreter session in the exploit module "wp_admin_shell_upload" not working

[japomarley]

Steps to reproduce

1. used exploit/unix/webapp/wp_admin_shell_upload ( tested it with every available payload )
2. typed run
3. the exploitation goes well and generate a new meterpreter session
4. metasploit gets stuck
5. try with Ctrl+C in order to exit from the session
6. get an error which tells that the exploit is interrupted by the user and failed
7. enter again in the session ( which is still alive and partially working )
8. able to access the target and use some common commands such as ls or cat but not able to use things like shell

I was doing a CTF (Mr Robot CTF on TryHackMe) and the target system was an Ubuntu machine. In this case the user I was using didn't have all the permissions.

Were you following a specific guide/tutorial or reading documentation?

I only used the info exploit/unix/webapp/wp_admin_shell_upload and understood how it works reading this.

Expected behavior

It should call a well-made meterpreter session with all of the normal functionalities.

Current behavior

It gets stuck waiting for deletion of the xxxxxxxx.php file uploaded in order to exploit the system. I then solved the challenge doing my own plugin with a reverse shell, so I think that the problems is not about the target system but occurs because the script get stuck waiting and can't call a well-made meterpreter session.

System stuff

Linux 5.7.0-kali1-amd64 x86_64 virtual machine on VirtualBox
4 CPU
8 GB RAM
50 GB of memory

Metasploit version

Framework: 6.0.3-dev-
Console : 6.0.3-dev-

I installed Metasploit with:

Kali package via apt

OS

Linux 5.7.0-kali1-amd64 x86_64

Screenshots

[anukaal]

Try to reinstall it once in the other directory

[OJ]

@GetRektBoy724 can you please stop with the Github spam unless you have something truly valuable to add, especially on old issues.

[GetRektBoy724]

@GetRektBoy724 can you please stop with the Github spam unless you have something truly valuable to add, especially on old issues.

wtf im not spamming

[github-actions[bot]]

Hi!

This issue has been left open with no activity for a while now.

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.

[github-actions[bot]]

Hi again!

It’s been 60 days since anything happened on this issue, so we are going to close it.
Please keep in mind that I’m only a robot, so if I’ve closed this issue in error please feel free to reopen this issue or create a new one if you need anything else.

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.