This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "SCG CMS Wordpress"

From OWASP
Jump to: navigation, search
Line 1: Line 1:
 
{{Template:OWASP Secure Configuration Guide}}
 
{{Template:OWASP Secure Configuration Guide}}
 +
 +
== Summary ==
 +
WordPress started in 2003 with a single bit of code to enhance the typography of everyday writing and with fewer users than you can count on your fingers and toes. Since then it has grown to be the largest self-hosted blogging tool in the world, used on millions of sites and seen by tens of millions of people every day.
 +
WordPress is web software you can use to create a beautiful website or blog. We like to say that WordPress is both free and priceless at the same time.
 +
 +
 +
== Common Misconfigurations ==
 +
 +
=== Misconfiguration 1 ===
 +
==== Description ====
 +
 +
%ProductName% allows unauthorized attacker to list all users of the system ...
 +
 +
// Detailed description of the impact. Is it enabled by default? Vulnerable versions.
 +
 +
==== How to test ====
 +
 +
In order to test for %Misconfiguration_1%, one should ...
 +
 +
// Proof-of-concept here. Please include the screenshots and widely known tools/scanners!
 +
 +
==== Remediation ====
 +
 +
Initial/common value of parameter "listUsers" from config.xml is set to "true".
 +
 +
To assess the vulnerability it is enough to change the value to false:
 +
 +
<pre>
 +
<security>
 +
<listUsers>false</listUsers>
 +
</security>
 +
</pre>
 +
 +
 +
 +
 
''' To be filled in in accordance to the template, some useful links: '''
 
''' To be filled in in accordance to the template, some useful links: '''
  

Revision as of 06:23, 10 January 2015

This article is part of the OWASP Secure Configuration Guide.
Back to the OWASP Secure Configuration Guide ToC: https://www.owasp.org/index.php/Secure_Configuration_Guide Back to the OWASP Secure Configuration Guide Project: https://www.owasp.org/index.php/OWASP_Secure_Configuration_Guide


Summary

WordPress started in 2003 with a single bit of code to enhance the typography of everyday writing and with fewer users than you can count on your fingers and toes. Since then it has grown to be the largest self-hosted blogging tool in the world, used on millions of sites and seen by tens of millions of people every day. WordPress is web software you can use to create a beautiful website or blog. We like to say that WordPress is both free and priceless at the same time.


Common Misconfigurations

Misconfiguration 1

Description

%ProductName% allows unauthorized attacker to list all users of the system ...

// Detailed description of the impact. Is it enabled by default? Vulnerable versions.

How to test

In order to test for %Misconfiguration_1%, one should ...

// Proof-of-concept here. Please include the screenshots and widely known tools/scanners!

Remediation

Initial/common value of parameter "listUsers" from config.xml is set to "true".

To assess the vulnerability it is enough to change the value to false:

<security>
	<listUsers>false</listUsers>
</security>



To be filled in in accordance to the template, some useful links:

http://codex.wordpress.org/Hardening_WordPress (consider writing only real security risks with good examples)


https://github.com/anantshri/wp-security (extract samples from here. keep them as code sections either for a plugin or for a theme functions.php, .htaccess or nginx config file)