Bug 1045416

Summary:	wordpress: information leakage and backdoor vulnerabilities in writing settings
Product:	[Other] Security Response	Reporter:	Ratul Gupta <ratulg>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	fedora, gwync, jrusnack, vkrizan
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-08 02:31:09 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1045420, 1045421
Bug Blocks:

Description Ratul Gupta 2013-12-20 11:34:01 UTC

It was found that the login and password from e-mail are saved in DB in plain text (unencrypted) in Writing Settings (http://site/wp-admin/options-writing.php), if this functionality is used. So by receiving data from DB via SQL Injection or Information Leakage vulnerability, or by receiving content of this page via XSS, or by accessing admin panel via any vulnerability, it's possible to get login and password from e-mail account.

Also, this functionality can be used as backdoor. When attacker's e-mail is set in options Writing Settings, from which the posts will be published at web site. With XSS code, with black SEO links, with malware code, etc.

References:
http://seclists.org/fulldisclosure/2013/Dec/135

Comment 1 Ratul Gupta 2013-12-20 11:37:52 UTC

Created wordpress tracking bugs for this issue:

Affects: fedora-all [bug 1045420]
Affects: epel-all [bug 1045421]

Comment 2 Ratul Gupta 2013-12-23 10:07:53 UTC

CVE Request:
http://seclists.org/oss-sec/2013/q4/538

Comment 4 Product Security DevOps Team 2019-06-08 02:31:09 UTC

This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.