CVE-2014-9292

jRSS Widget <= 1.2 - Server-Side Request Forgery

2014-05-28 00:00

Strategic Overview

Status: Unpatched
Affected Plugin: jRSS Widget
Affected Version: <= 1.2
CVSS: 7.5High
Weakness type: CWE-918 · Server-Side Request Forgery (SSRF)
CVE: CVE-2014-9292

At a glance

CVE-2014-9292 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in the jRSS Widget WordPress plugin, affecting versions <= 1.2. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed May 2014, reported by Prajal Kulkarni.

Vulnerability Overview

Server-side request forgery (SSRF) vulnerability in proxy.php in the jRSS Widget plugin 1.2 and earlier for WordPress allows remote attackers to trigger outbound requests and enumerate open ports via the url parameter.

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, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-918: Server-Side Request Forgery (SSRF)

Reaching this weakness in jRSS Widget <= 1.2 takes a caller who can reach the endpoint. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.

The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. No fixed build of this plugin is recorded for jRSS Widget yet, so installs running <= 1.2 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 jRSS Widget: 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

https://www.cve.org/CVERecord?id=CVE-2014-9292 https://www.wordfence.com/threat-intel/vulnerabilities/id/1680078c-0dbe-4586-b793-3bf2ddea96ba https://nvd.nist.gov/vuln/detail/CVE-2014-9292

CVSS Vector

7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityNone
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/