Encrypted Blog <= 0.0.6.2 - Open Redirect

2013-08-28 00:00
Keith Makan

Strategic Overview

Status
Patched in 0.0.6.6
Affected Plugin
Encrypted Blog
Affected Version
<= 0.0.6.2
CVSS
6.1Medium
Weakness type
CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
CVE
CVE pending
View all Encrypted Blog vulnerabilities

At a glance

This record tracks a medium-severity URL Redirection to Untrusted Site ('Open Redirect') vulnerability in the Encrypted Blog WordPress plugin, affecting versions <= 0.0.6.2. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 0.0.6.6; sites on affected versions should update now. Disclosed August 2013, reported by Keith Makan.

Vulnerability Overview

The Encrypted Blog plugin for WordPress is vulnerable to Open Redirect in versions up to, and including, 0.0.6.2 via the 'redirect_to' parameter in the 'encrypt_blog_form.php' file. This makes it possible for unauthenticated attackers to potentially redirect other users to arbitrary websites where they can gather sensitive information.

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')

Encrypted Blog <= 0.0.6.2 carries this weakness at redirect_to, 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. For Encrypted Blog the fix is 0.0.6.6: builds <= 0.0.6.2 are affected, anything from 0.0.6.6 onward is not.

Remediation

Update to version 0.0.6.6, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Encrypted Blog: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Encrypted Blog 0.0.6.6 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/33a26790-1fb8-4088-87dc-e026a28f205d

Related records

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