2Download Connector for 2DL Hosted Checkout

2Download Connector for 2DL Hosted Checkout has one disclosed vulnerability in the WordSec catalog, all reported in 2026; it is fixed as of August 2026. Their average CVSS score is 5.3, and the most serious one scores 5.3 out of 10.

The most common weakness is Missing Authorization, behind 1 of the records (100%).

The one issue recorded for 2Download Connector for 2DL Hosted Checkout has a vendor fix available, so running the current release closes it.

All of these findings were reported by Mohamed Haidar. The current release is tested up to WordPress 6.9.7.

Strategic Overview

Avg CVSSMedium
5.3/ 10
Patch Coverage100%
Open

0

Fixed

1

Get automatic notifications for all 2Download Connector for 2DL Hosted Checkout vulnerabilities before they are exploited.

Highest severity on recordCVSS 5.3CVE-2026-6798

2Download Connector for 2DL Hosted Checkout <= 0.1.5 - Missing Authorization to Unauthenticated Sensitive Customer Subscription Data Exposure via 'ToDownload_email' Parameter

Read the full analysis

Vulnerability Records

1 records
Plugin Profile
Latestv0.1.8

2Download Connector for 2DL Hosted Checkout

2download

Author

2download

5.0(1)
100/100
Last Updated
2026-05-06 (3mo ago)
Active Installs
0+
Downloads
548
Requires WP
6.0+
Requires PHP
8.1+
Tested up to
WP 6.9.7
Created
2026-01-19 (7mo ago)

2Download Connector for 2DL Hosted Checkout integrates your WordPress site with 2DL hosted services (2dl.app). Checkout sessions and receipts are created/fetched via 2dl.app. Subscription tier (Standard/Pro/Studio) is managed on 2dl.app. This plugin does not require payment secret keys or webhooks on your WordPress site. This plugin does not include any license-key locks for local functionality. Subscription billing (if used) is handled by the 2dl.app hosted service. Shortcodes: – [ToDownload_storefront] – storefront listings – [ToDownload_cart] – cart – [ToDownload_checkout] – checkout (redirects to hosted checkout) – [ToDownload_account] – receipts / account view External services This plugin communicates with 2DL hosted services to enable hosted checkout, secure delivery, and Connect onboarding/status. Domain(s) the plugin may connect to: https://2dl.app (default) https://staging.2dl.app (optional, if your WordPress site is configured to use staging) https://wp.2dl.app and subdomains (optional, used by the hosted WordPress connector environment) The exact base URL is configured by your site admin in the plugin settings. What the service is / what it is used for: 2DL hosted services (2dl.app) Purpose: create hosted checkout sessions, look up receipts/licenses, and manage seller onboarding/status. Data sent and when (depending on configuration and flow): When creating a hosted checkout session: store/product identifiers and redirect URLs (for example store_public_id, product_public_id, success_url, cancel_url). When looking up receipts/licenses: checkout session ID (for example session_id). When starting Connect onboarding via 2DL (admin/seller action): store identifier plus redirect URLs (for example store_public_id, return_url, refresh_url). When checking Connect status (admin/seller action): store identifier. For authenticated server-to-server requests: a Store API key in the Authorization: Bearer ... header. Optional request tracing headers. See our policies: – Privacy Policy: https://2dl.app/privacy – Terms of Service: https://2dl.app/terms – Refund & Dispute Policy: https://2dl.app/refunds Payments are handled by 2dl.app. This plugin does not send payment-processor secret keys from your WordPress site. Privacy This plugin sends data to 2dl.app to perform hosted checkout and receipt/license lookups. See the “External services” section above for details about what data is transmitted and when. If you use this plugin, you should review and link to your site’s own privacy policy, and include 2dl.app as a service provider where applicable. Hosting requirements 2DL runs inside your WordPress site, so upload limits are controlled by your web host (PHP/nginx), not by 2DL. Recommended settings: upload_max_filesize: 64M or higher post_max_size: 64M or higher (must be >= upload_max_filesize) memory_limit: 256M If using nginx: client_max_body_size 64M; If you see an upload limit like 2–8MB in WordPress (Media Library, Site Health), increase the limits in your hosting control panel. Cloudways example: Server → Settings & Packages → PHP: set upload_max_filesize and post_max_size. Manage Services: restart PHP-FPM (and nginx if you changed nginx settings). Update Notice 0.1.8 Security follow-up with Plugin Check readme metadata fix. 0.1.7 Security follow-up with Plugin Check output escaping fix. 0.1.6 Security update. Guest account lookups now require a signed email token. 0.1.5 Recommended update. 0.1.1 Recommended update.

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C