The WebDorado Contact Form Builder plugin before 1.0.69 for WordPress allows CSRF via the wp-admin/admin-ajax.php action parameter, with resultant local file inclusion via directory traversal, because there can be a discrepancy between the $_POST['action'] value and the $_GET['action'] value, and the latter is unsanitized.

*   Details
*   Reviews
*   Development

Create responsive FREE contact forms with multiple templates and themes.

Quick way to build a form without taking rocket science classes.

I have absolutely no complaints. It's taken me a bit to find my way around, but the program is working like a well-oiled engine.

Does the work, is configurable, works fine!

I've had the form on my website since launching it and it's been very helpful for us to collate and collect information.

thanks a lot for free use in this configuration. It works and good for individual Forms.

easy to use. simple and efficient.

Read all 186 reviews

“WDContactFormBuilder” is open source software. The following people have contributed to this plugin.

Contributors

*    webdorado

CVE-2019-11557: WDContactFormBuilder

In the wp-google-maps plugin before 7.11.18 for WordPress, includes/class.rest-api.php in the REST API does not sanitize field names before a SELECT statement.

CVE-2019-10692: WP Go Maps (formerly WP Google Maps)

CVE-2019-10692: WP Google Maps

An Information Disclosure / Data Modification issue exists in article2pdf_getfile.php in the article2pdf Wordpress plugin 0.24, 0.25, 0.26, 0.27. A URL can be constructed which allows overriding the PDF file's path leading to any PDF whose path is known and which is readable to the web server can be downloaded. The file will be deleted after download if the web server has permission to do so. For PHP versions before 5.3, any file can be read by null terminating the string left of the file extension.

Skip to content

*   When visiting the PDF download link which the original PDF generation  
    link redirects to, the file path is constructed from a combination of  
    fixed strings and the strings provided via the query string of the  
    download URL. The download URL has the form  
    http://www.example.com/wp-content/plugins/article2pdf/article2pdf\_getfile.php?p=xxx&r=yyy&d=zzz  
    where xxx is a base64 encoded absolute string, xxx is a short hex hash  
    and zzz is the base64 encoded URL title slug of the post the PDF was  
    generated from. While the plugin attempts to sanitise these input  
    parameters to not allow path traversal, this sanitisation is  
    insufficient and can be fully or partially circumvented depending on  
    the PHP version the WordPress instance is running on.
    
    In the case of PHP version <5.3 it is possible to read any file the  
    user the plugin is executed under has read access to by just encoding  
    the full file path in the parameter “d” and terminating that string  
    with a null-byte. The parameter “p” must not be empty but can contain  
    any value. The parameter “r” may be empty but its value is of no  
    significance. If the user that the script is executed as has write  
    access to the file or the directory it is stored in, the file will be  
    deleted after it has been downloaded. If the user has no write access,  
    an error message may be shown at the end of the file contents  
    offered which discloses the WordPress instance’s install directory on  
    the server.
    
    In the case of PHP version >=5.3, null-termination will no longer cut  
    off the string. As the generated file name ends with a fixed string  
    “.pdf”, only files with that file ending can be read. The parameter “d”  
    may be any directory on the server. The parameter “p” needs to contain  
    8 backspace characters to delete a prepended fixed string from the file  
    name while the parameter “r” must contain exactly one backspace. The  
    actual file name (without the “.pdf”) can then be appended to the  
    backspaces in either parameter “p” or parameter “r”. It is also  
    possible to have “p” contain one random character and then have 10  
    backspace characters followed by the actual file name (again,  
    without the “.pdf”) stored in parameter “r”.
    

*   The topic ‘PDF download path improperly sanitised’ is closed to new replies.

CVE-2019-1010257: PDF download path improperly sanitised

A disk space or quota exhaustion issue exists in article2pdf_getfile.php in the article2pdf Wordpress plugin 0.24, 0.25, 0.26, 0.27. Visiting PDF generation link but not following the redirect will leave behind a PDF file on disk which will never be deleted by the plug-in.

**Bugtraq mailing list archives**

_From_: Christian Lerrahn <cybersec () drwaryaa com>  
_Date_: Tue, 26 Mar 2019 12:31:25 +1100  

Product: article2pdf (Wordpress plug-in)
Product Website: https://wordpress.org/plugins/article2pdf/
Affected Versions: 0.24 and greater

The following vulnerabilities were found in a code review of the plug-in. An attempt to contact the plug-in maintainer on 8 December 2018 was unsuccessful. The Wordpress security team disabled downloads

of the plug-in upon notification on 8 January 2019.

I would like to thank Ken Johnson (@cktricky) and Set Law (@sethlaw) whose course "Seth & Ken's Excellent Adventures in Secure Code Review" sparked my interest in reviewing code for

vulnerabilities.

\[CVE-2019-1000031\] Generated PDF file is only removed after download which is initiated by a redirect

\=====================================================================================================
Type:
-----
Resource Exhaustion

Description:
-----------
The plugin generates a PDF version of a post/article when a link of the
form

https://www.example.com/.../my-post-title/?article2pdf=1

is visited. The response to this initial request is a redirect to a link
like

http://www.example.com/wp-content/plugins/article2pdf/article2pdf\_getfile.php?p=xxx&r=yyy&d=zzz

which will then return the PDF file contents and subsequently delete
the file.

As the deletion is coupled with the download but the download is
initiated by a different request than the one which creates the file,
visiting the link which creates the file and not following the redirect
results in the file not being deleted. These files can then accumulate
and potentially exhaust the available disk space.

Depending on the server setup, space exhaustion of a hard drive or hard
drive partition or even just a disk quota can result in denial of
service even for unrelated services on the same machine which rely on
the same resource.

This issue was originally reported on the plugin's bug tracker \[2\] but
never identified as a vulnerability.

Exploit
-------
Repeatedly visit a PDF generation link the plugin provides without ever
following the redirect to exhaust disk space.

\[CVE-2019-1010257\] PDF file download path is constructed from insufficiently sanitised user input

\=================================================================================================
Type:
-----
Information Disclosure / File Deletion

Description:
------------
When visiting the PDF download link which the original PDF generation
link redirects to, the file path is constructed from a combination of
fixed strings and the strings provided via the query string of the
download URL. The download URL has the form

http://www.example.com/wp-content/plugins/article2pdf/article2pdf\_getfile.php?p=xxx&r=yyy&d=zzz

where xxx is a base64 encoded absolute string, xxx is a short hex hash
and zzz is the base64 encoded URL title slug of the post the PDF was
generated from. While the plugin attempts to sanitise these input
parameters to not allow path traversal, this sanitisation is
insufficient and can be fully or partially circumvented depending on
the PHP version the Wordpress instance is running on.

In the case of PHP version <5.3 it is possible to read any file the
user the plugin is executed under has read access to by just encoding
the full file path in the parameter "d" and terminating that string
with a null-byte. The parameter "p" must not be empty but can contain
any value. The parameter "r" may be empty but its value is of no
significance. If the user that the script is executed as has write
access to the file or the directory it is stored in, the file will be
deleted after it has been downloaded. If the user has no write access,
an error message may be shown at the end of the file contents
offered which discloses the Wordpress instance's install directory on
the server.

In the case of PHP version >=5.3, null-termination will no longer cut
off the string. As the generated file name ends with a fixed string
".pdf", only files with that file ending can be read. The parameter "d"
may be any directory on the server. The parameter "p" needs to contain
8 backspace characters to delete a prepended fixed string from the file
name while the parameter "r" must contain exactly one backspace. The
actual file name (without the ".pdf") can then be appended to the
backspaces in either parameter "p" or parameter "r". It is also
possible to have "p" contain one random character and then have 10
backspace characters followed by the actual file name (again,
without the ".pdf") stored in parameter "r".

The information above can also be found on the plug-in's issue tracker \[3\].

Exploit:
--------
On PHP <5.3, a specially crafted link like

http://php52.example.com/wp-content/plugins/article2pdf/article2pdf\_getfile.php?p=YQ==&r=&d=L2V0Yy9wYXNzd2QA

will download the server's /etc/passwd file.

On PHP >=5.3, a specially crafted link like

http://www.example.com/wp-content/plugins/article2pdf/article2pdf\_getfile.php?p=CAgICAgICAg=&r=%08test&d=L3RtcA==

will return the contents of the file "/tmp/test.pdf" and delete the
file if the user the script is executed as has permissions to do so.

The link used above can be generated using a few lines of PHP:

    <?php
    $d52 = base64\_encode("/etc/passwd\\0");
    $p52 = base64\_encode("a");
    $r52 = "";

echo "http://www.example.com/wp-content/plugins/article2pdf/article2pdf\_getfile.php?p=${p52}&r=${r52}&d=${d52}\\n";;

    $d53 = base64\_encode("/tmp");
    $p53\_raw = "";
    for ($i=0;$i<8; $i++) $p53\_raw .= chr(8);
    $p53 = base64\_encode($p53\_raw);
    $r53 = "%08test";

echo "http://www.example.com/wp-content/plugins/article2pdf/article2pdf\_getfile.php?p=${p53}&r=${r53}&d=${d53}\\n";;

\[1\] https://wordpress.org/plugins/article2pdf/

\[2\] https://wordpress.org/support/topic/plugin-article2pdf-temporary-files-filling-up-server-space/ \[3\] https://wordpress.org/support/topic/pdf-download-path-improperly-sanitised/

**Current thread:**

*   **\[article2pdf (Wordpress plug-in)\] Multiple vulnerabilities (CVE-2019-1000031, CVE-2019-1010257)** _Christian Lerrahn (Mar 26)_

CVE-2019-1000031: [article2pdf (Wordpress plug-in)] Multiple vulnerabilities (CVE-2019-1000031, CVE-2019-1010257)

The wp-google-maps plugin before 7.10.43 for WordPress has XSS via the wp-admin/admin.php PATH_INFO.

*   Vulnerability: XSS
*   Affected Software: wpGoogleMaps (400,000+ active installations)
*   Affected Version: 7.10.41
*   Patched Version: 7.10.43
*   Risk: Medium
*   Vendor Contacted: 10/25/2018
*   Vendor Fix: 10/31/2018
*   Public Disclosure: 02/05/2019

**CVSS**

6.1 Medium CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

**Details**

The wpGoogleMaps WordPress plugin is vulnerable to reflected XSS as it echoes PHP\_SELF without proper encoding.

Successful exploitation allows an attacker to execute JavaScript in the context of the application in the name of an attacked user. This in turn enables an attacker to bypass CSRF protection and thus perform any actions the legitimate user can perform, as well as read data which the user can access.

**Proof of Concept**

    http://192.168.0.103/wordpress/wp-admin/admin.php/'"><img src=x onerror=alert(1)>?page=wp-google-maps-menu&action=foo
    

**Code**

    wp-google-maps/wpGoogleMaps.php                          
    <input type='hidden' name='http_referer' value='".$_SERVER['PHP_SELF']."' />
    

**Timeline**

*   10/25/2018 Sent advisory
*   10/25/2018 Vendor confirms and releases fix
*   10/25/2018 Suggested improvement for fix
*   10/31/2018 Vendor releases improved fix
*   02/05/2019 Disclosure

CVE-2019-9912: wpGoogleMaps 7.10.41 - Reflected XSS (WordPress Plugin)

The wp-live-chat-support plugin before 8.0.18 for WordPress has wp-admin/admin.php?page=wplivechat-menu-gdpr-page term XSS.

*   Vulnerability: XSS
*   Affected Software: WP Live Chat Support (60,000+ active installations)
*   Affected Version: 8.0.17
*   Patched Version: 8.0.18
*   Risk: Medium
*   Vendor Contacted: 10/31/2018
*   Vendor Fix: 11/01/2018
*   Public Disclosure: 02/05/2019

**CVSS**

6.1 Medium CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

**Details**

The WP Live Chat Support WordPress plugin is vulnerable to reflected XSS as it echoes the term parameter without proper encoding.

Successful exploitation allows an attacker to execute JavaScript in the context of the application in the name of an attacked user. This in turn enables an attacker to bypass CSRF protection and thus perform any actions the legitimate user can perform, as well as read data which the user can access.

**Proof of Concept**

    http://192.168.0.103/wordpress/wp-admin/admin.php?page=wplivechat-menu-gdpr-page&term='"><img+src%3Dx+onerror%3Dalert(1)>
    

**Code**

    wp-live-chat-support/modules/gdpr.php:                      <a class='button' href='?page=wplivechat-menu-gdpr-page&term=<?php echo($_GET["term"]); ?>&action=delete&filter=<?php echo $action_action_filter; ?>&id=<?php echo $cid; ?>'><?php echo $delete_button_text; ?></a>
    wp-live-chat-support/modules/gdpr.php:                      <a class='button button-primary' href='?page=wplivechat-menu-gdpr-page&term=<?php echo($_GET["term"]); ?>&action=download&filter=<?php echo $action_action_filter; ?>&id=<?php echo $cid; ?>'><?php echo $download_button_text; ?></a>
    

**Further**

In addition to the reflected XSS issue, there is a self-XSS issue in the client-side input form, which can be triggered by entering '"><img src=x onerror=alert(1)>. Self-XSS may be exploitable via social engineering or Clickjacking.

**Timeline**

*   10/31/2018 Requested email address via contact form
*   10/31/2018 Vendor responds, advisory sent
*   11/01/2018 Vendor releases fix
*   02/05/2019 Confirmed fix & Disclosure

CVE-2019-9913: WP Live Chat Support 8.0.17 - Reflected XSS (WordPress Plugin)

The "Donation Plugin and Fundraising Platform" plugin before 2.3.1 for WordPress has wp-admin/edit.php csv XSS.

*   Vulnerability: XSS
*   Affected Software: Give (50,000+ active installations)
*   Affected Version: 2.3.0
*   Patched Version: 2.3.1
*   Risk: Medium
*   Vendor Contacted: 11/24/2018
*   Vendor Fix: 12/13/2018
*   Public Disclosure: 02/05/2019

**CVSS**

6.1 Medium CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

**Details**

The Give WordPress plugin is vulnerable to reflected XSS as it echoes various parameter without proper encoding.

Successful exploitation allows an attacker to execute JavaScript in the context of the application in the name of an attacked user. This in turn enables an attacker to bypass CSRF protection and thus perform any actions the legitimate user can perform, as well as read data which the user can access.

**Proof of Concept**

    http://localhost/wordpress/wp-admin/edit.php?post_type=give_forms&page=give-tools&tab=import&importer-type=import_donations&step=3&mapto%5B0%5D=email&mapto%5B1%5D=first_name&mapto%5B2%5D=amount&mapto%5B3%5D=form_id&csv='"><img+src%3dx+onerror%3dalert(1)>
    

**Code**

    public function start_import() {
        [...]
        <input type="hidden" value='<?php echo maybe_serialize( $_REQUEST['mapto'] ); ?>' name="mapto"
       class="mapto">
        <input type="hidden" value="<?php echo $_REQUEST['csv']; ?>" name="csv" class="csv">
        <input type="hidden" value="<?php echo $_REQUEST['mode']; ?>" name="mode" class="mode">
        <input type="hidden" value="<?php echo $_REQUEST['create_user']; ?>" name="create_user"
       class="create_user">
        <input type="hidden" value="<?php echo $_REQUEST['delete_csv']; ?>" name="delete_csv"
       class="delete_csv">
        <input type="hidden" value="<?php echo $delimiter; ?>" name="delimiter">
        <input type="hidden" value="<?php echo absint( $_REQUEST['dry_run'] ); ?>" name="dry_run">
    

**Timeline**

*   11/24/2018 Asked for email address via contact form
*   11/24/2018 Vendor responds, advisory sent
*   12/13/2018 Vendor releases fix
*   02/05/2019 Confirmed fix & Disclosure

CVE-2019-9909: Give 2.3.0 - Reflected XSS (WordPress Plugin)

An authenticated shell command injection issue has been discovered in Raisecom ISCOM HT803G-U, HT803G-W, HT803G-1GE, and HT803G GPON products with the firmware version ISCOMHT803G-U_2.0.0_140521_R4.1.47.002 or below, The values of the newpass and confpass parameters in /bin/WebMGR are used in a system call in the firmware. Because there is no user input validation, this leads to authenticated code execution on the device.

This website will mainly for manageing advisories which i create on day to day basis and for My CVE Database.

CVE ID

VENDOR

ISSUE

Reference

CVE-2015-1437

ASUS

XSS In Asus Router

https://nvd.nist.gov/vuln/detail/CVE-2015-1437

CVE-2015-1614

WordPress

XSRF(CSRF+XSS)

https://nvd.nist.gov/vuln/detail/CVE-2015-1614

CVE-2015-2755

WordPress

XSS / CSRF

https://nvd.nist.gov/vuln/detail/CVE-2015-2755

CVE-2016-9259

Tenable

Nessus XSS

https://www.tenable.com/security/tns-2016-17

CVE-2016-9261

Tenable

LCE XSS

https://www.tenable.com/security/tns-2016-18

CVE-2016-7103

Tenable

Security Centre XSS

https://www.tenable.com/security/tns-2016-19

CVE-2016-7103

Tenable

PVS XSS

https://www.tenable.com/security/tns-2016-20

CVE-2018-19524

Skyworth

Stack Overflow in Gpon Devices

https://s3curityb3ast.github.io/KSA-Dev-001.md

CVE-2018-19525

Systorme

Account takeover

https://s3curityb3ast.github.io/KSA-Dev-002.md

CVE-2019-7383

Systorme

RCE via shell upload

https://s3curityb3ast.github.io/KSA-Dev-003.md

CVE-2019-7387

Systorme

LFI

https://s3curityb3ast.github.io/KSA-Dev-004.md

CVE-2019-7384

Raisecom

Auth RCE

https://s3curityb3ast.github.io/KSA-Dev-005.md

CVE-2019-7385

Raisecom

Auth RCE

https://s3curityb3ast.github.io/KSA-Dev-006.md

CVE-2019-7386

NOKIA & HDM & KAI

Buffer overflow

https://s3curityb3ast.github.io/KSA-Dev-007.md

CVE-2020-21884

UniBox

XSRF

https://s3curityb3ast.github.io/KSA-Dev-008.txt

CVE-2020-21883

Unibox

Auth RCE

https://s3curityb3ast.github.io/KSA-Dev-009.txt

CVE-2021-3275

TP Link

Unauth-XSRF

https://s3curityb3ast.github.io/KSA-Dev-010.md

CVE-2021-25326

Skyworth

Info\_Disc

https://s3curityb3ast.github.io/KSA-Dev-012.txt

CVE-2021-25327

Skyworth

XSRF

https://s3curityb3ast.github.io/KSA-Dev-011.txt

CVE-2021-25328

Skyworth

Auth-RCE

https://s3curityb3ast.github.io/KSA-Dev-010.txt

CVE-2019-7385: Welcome to Kaustubh security advisories

Cross-site request forgery (CSRF) vulnerability in Smart Forms 2.6.15 and earlier allows remote attackers to hijack the authentication of administrators via a specially crafted page.

Tag

#wordpress