CVE-2015-6523

Portfolio Plugin < 1.05 - Cross-Site Request Forgery

2015-07-20 00:00

Strategic Overview

Status: Patched in 1.05
Affected Plugin: Portfolio Plugin
Affected Version: < 1.05
CVSS: 6.3Medium
Weakness type: CWE-352 · Cross-Site Request Forgery (CSRF)
CVE: CVE-2015-6523

View all Portfolio Plugin vulnerabilities

At a glance

CVE-2015-6523 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Portfolio Plugin WordPress plugin, affecting versions < 1.05. It carries a CVSS score of 6.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.05; sites on affected versions should update now. Disclosed July 2015, reported by Nitin Venkatesh.

Vulnerability Overview

Cross-site request forgery (CSRF) vulnerability in the Portfolio plugin before 1.05 for WordPress allows remote attackers to hijack the authentication of administrators for requests that have unspecified impact via a request to the instagram-portfolio page in wp-admin/options-general.php.

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-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Portfolio Plugin < 1.05 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Portfolio Plugin the fix is 1.05: builds < 1.05 are affected, anything from 1.05 onward is not.

Remediation

Update to version 1.05, or a newer patched version

How does WordSec protect against this?

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

Firewall
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2015-6523 https://www.wordfence.com/threat-intel/vulnerabilities/id/4fb0c069-ea6d-4eff-851e-b41c34b41152 https://nvd.nist.gov/vuln/detail/CVE-2015-6523

Related records

Same weakness class

4.3CVE-2012-10017: Portfolio Plugin <= 2.04 Cross-Site Request ForgeryCVE-2012-10017

CVSS Vector

6.3

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

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionRequired
ScopeUnchanged
ConfidentialityLow
IntegrityLow
AvailabilityLow

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/