Strategic Overview
- Status
- Unpatched
- Affected Theme
- T1 Theme
- Affected Version
<= 19.0- CVSS
- 4.3Medium
- Weakness type
- CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
- CVE
CVE-2023-3771
At a glance
CVE-2023-3771 is a medium-severity URL Redirection to Untrusted Site ('Open Redirect') vulnerability in the T1 Theme WordPress theme, affecting versions <= 19.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed July 2023, reported by Vishal Barot vFlexo.
Vulnerability Overview
The T1 Theme for WordPress is vulnerable to Open Redirect in versions up to, and including, 19.0. This is due to insufficient validation on the redirect url supplied via the 'url_js' parameter. This makes it possible for unauthenticated attackers to redirect users to potentially malicious sites if they can successfully trick them into performing an action.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-601: URL Redirection to Untrusted Site ('Open Redirect')
T1 Theme <= 19.0 carries this weakness at url_js, and reaching it takes a caller who can reach the endpoint. An open redirect is a page that takes a destination from the request and sends the browser there without checking that the destination belongs to the site.
A link that starts on a trusted domain finishes on an attacker's, which is what makes phishing and consent-screen abuse credible to the person clicking it. No fixed build of this theme is recorded for T1 Theme yet, so installs running <= 19.0 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
The attempt arrives as an ordinary request to T1 Theme: WordSec's web application firewall inspects request payloads before WordPress loads them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C