Configuration script does not allow apostrophes, blank prefixes

[incaren]

When using the wp-admin/setup-config.php to create a configuration file automatically, the following do not work properly:

1. Using a MySQL username with an apostrophe.
2. Using a MySQL password with an apostrophe.
3. Using a blank prefix.

The expected outcomes is that Wordpress:

1. Runs
2. Uses tables with no prefix (not swp)

The actual outcome is that the configuration file has errors due to unclosed apostrophes, and the tables created start with wp_. Adding addslashes() to certain statements and removing

Line 152:

if (empty($prefix)) $prefix = 'wp_';

would correct this.

[nacin]

1 and 2 look fine, but I don't think we should simply create tables without a prefix if the field gets cleared.

[incaren]

Replying to nacin:

1 and 2 look fine, but I don't think we should simply create tables without a prefix if the field gets cleared.

Please correct me if I'm wrong, but if the Wordpress instance is getting its own database, there often is no need for a prefix. This applied for our use case at least.

[nacin]

It doesn't need a prefix, but it doesn't hurt either.

[anthonycole]

Submitted first patch incorrectly

[dd32]

Related: #16229

Like nacin I don't believe we should support a blank prefix in the wp-config.php wizard, it should be throwing an error in that case instead. Being able to set a blank/empty prefix via a manual file creation is a bit more deliberate

Also note, Table prefixes are used in more than just table names, they're also used for per-site capabilities(Multisite and shared user tables, etc).

The patches here fix ' being in a username or password, but not the database name, but also break " being in a password. As an addition \ would also break it (as it's not escaped properly either).

Looking at this, it looks like addcslashes($.., "\\'"); is what should be used, which escapes both \ and ' whilst leaving " alone. An example password would be: 1'2\3"4 which should end up like this: define('DB_PASSWORD', '1\'2\\3"4');

Attached is a patch for testing based on addcslashes and erroring out on an empty prefix

[SergeyBiryukov]

Replying to dd32:

Attached is a patch for testing based on addcslashes and erroring out on an empty prefix

13839.2.diff​ still doesn't allow apostrophes in a password, resulting in "Error establishing a database connection".

In 13839.3.diff​ I've added stripslashes() before trying to connect to a database, and it seems to works properly with the example password of 1'2\3"4.

[dd32]

13839.2.diff still doesn't allow apostrophes in a password, resulting in "Error establishing a database connection".

I had to edit the patch to remove some other changes, so I must've removed too much in the process.

I'm not really happy with the patch to start with, the changes to wp_die() are half-baked in this patch, the refactoring in #18180 is really needed IMO.

I'm going to rework the stripslashes()/addcslashes() changes specifically from the patch and go from there I think, That'll at least fix this tickets main issue. For consistancy, We should probably apply this to the Hostname and the Prefix as well (as noted in #18180) even although Apostrophes should never be in a hostname.

[nacin]

Would a prefix that requires slashes even work? I mean, that seems like most queries would then break. We don't quote tables in most of our SQL.

[dd32]

Would a prefix that requires slashes even work?

Nope. And it shouldn't be able to be set either, as there's a check for a-z0-9, I was purely going for code consistency there, but we can probably just play it safe and ignore the slashing there..

[SergeyBiryukov]

Closed #19547 as a duplicate.

[ryan]

Don't we need to run wp_magic_quotes() before doing unconditional adds and strips since setup-config.php is not loading wp-settings.php?

[SergeyBiryukov]

13839.4.diff​ is the refreshed the patch after the changes in #18180. Added wp_magic_quotes() (requires formatting.php).

13839.5.diff​ adds/strips slashes for all the five variables for consistency, as suggested by dd32.

See also #19970 for empty prefix warning with a manually created wp-config.php.

[ryan]

Let's toss in wp_unregister_GLOBALS() as well.

[SergeyBiryukov]

Replying to ryan:

Let's toss in wp_unregister_GLOBALS() as well.

Done in 13839.6.diff​.

[nacin]

In [20482]:

Do sanity checks for register_globals and magic quotes in setup-config.php. see #13839.

[nacin]

In [20483]:

Escape special characters when outputting DB failures. see #13839.

[nacin]

[20482] and [20483] are both good candidates to be backported to the 3.3 branch.

[nacin]

In [20484]:

Do sanity checks for register_globals and magic quotes in setup-config.php. see #13839 for the 3.3 branch.

[nacin]

In [20485]:

Escape special characters when outputting DB failures. see #13839 for the 3.3 branch.

[ryan]

In [20661]:

setup-config.php cleanups

• Don't allow an empty prefix
• Make slashing consistent and sane

Props SergeyBiryukov
Fixes #13839