It's better when it's simple

User Tools

Site Tools


Translations of this page?:

Learn about DokuWiki

Advanced Use

Corporate Use

Our Community

Follow us on Facebook, Twitter and other social networks.



DokuWiki is a web application and is often used on public servers, reachable from the Internet. This means it is at a greater risk to be attacked by malicious people than, for example, a local application on your desktop system.

DokuWiki is developed with security in mind. We try to find a balance between user-friendliness and security but favor security when no satisfying compromise can be found.

This page should give you an overview on what aspects you should have an eye on to make sure your DokuWiki is secure.

Reporting and Notifications

When you discover a security issue in DokuWiki, please notify us. The preferred ways to do so are:

The first two ways should be preferred except for very serious bugs where making the bug public before a patch is available could endanger DokuWiki installations world wide.

All previous security issues can be seen in the bugtracking system.

Depending on the severity of a found security issue it will be fixed in a future release (on very minor issues) or a bugfix release will be made. In the latter case users will be informed through the update check mechanism.

You should always run the most current release of DokuWiki as there are no security fixes released for older versions.

Web Access Security

DokuWiki stores configuration and page data in files. These files should never be accessible directly from the web. The distribution tarball contains a set of .htaccess files which usually tell the Apache web server to deny access to certain directories.

If you don't use the Apache web server or your Apache does not use .htaccess files you need to manually secure your installation

The following directories should not be accessible from the web:

  • data
  • conf
  • bin
  • inc (isn't dangerous when accessible, though)

To check if you need to adjust the access permissions try to access You should not get access to that file this way.

(More about permissions - install:permissions - but it does not deal with the lack of detailed information about Dokuwiki's directory permissions. I mean about a short form of presentation, e.g. “Above four directories - /data, /conf, /bin, /inc - need to have 0700 permissions” etc.)

If your directories are not properly secured, read the following subsections on how to do that.

Deny Directory Access in Apache

The simplest way is to enable .htaccess support in your Apache configuration. Please see the Apache .htaccess Tutorial.

DokuWiki already comes with correctly configured .htaccess files. The contents of a .htaccess file to block all access to the directory it is in should be as follows (valid for both Apache 2.2 and 2.4):

<IfModule !mod_authz_core.c>
  Order deny,allow
  Deny from all
<IfModule mod_authz_core.c>
  Require all denied

Remark : Using apache2 on Ubuntu, the .htaccess does not work until you activate the 'mod_rewrite' in apache2 (sudo a2enmod rewrite && sudo service apache2 restart)

It seems that Apache2 in general, or it might be specifically to Ubuntu, is configured slightly differently than Apache1.x.

In the /etc/apache2/sites-available (or you need to modify the file default, e.g. 000-default.conf) (or the file default-ssl if you use https rather than http)

There you'll find:

NameVirtualHost *
<VirtualHost *>

        DocumentRoot /var/www/
        <Directory />
                Options FollowSymLinks
                AllowOverride None
        <Directory /var/www/>
                Options Indexes FollowSymLinks MultiViews
                AllowOverride none
                Order allow,deny
                allow from all

Default for AllowOverride in the <Directory /var/www/> is (double) none, should be (double) all

/etc/init.d/apache2 reload to refresh your apache configuration and your .htaccess files should now work.

:!:/etc/init.d/apache2 reload may not work. You can try sudo service apache2 restart instead.

(See for the full thread)

[you can make this change also for the particular directory containing your DokuWiki installation, ie. /var/www/path-to-dokuwiki instead of changing that globally]

The other way is to use LocationMatch directive inside VirtualHost definition - it's a little bit more efficient than .htaccess. Just below Directory directive add:

<LocationMatch "/(data|conf|bin|inc)/">
    Order allow,deny
    Deny from all
    Satisfy All

However see the “What to use When” section here for a statement that “Location” directives should not be used for protecting filesystem objects, only virtual (e.g. database-generated) paths. IMO if .htaccess isn't available or sufficient, then putting directory-specific restrictions directly in the hosts conf file would be the safest approach. This seems a solid approach - but this document should be “canonical”.

The above could cause a problem if you have another “root” that includes the directories data|conf|bin|inc. For example another wiki installation. You can avoid this problem by extending your LocationMatch within your wiki installation folder.

        <Directory /var/www/dokuwiki>
            order deny,allow
            allow from all

        <LocationMatch "/(data|conf|bin|inc)/">
            order allow,deny
            deny from all
            satisfy all

Deny Directory Access in IIS

Access to the mentioned directories can be disabled in IIS' configuration settings.

In IIS 8+

(Windows 8(.1) and Servers 2012 and 2012R2):

  1. select “IIS Request Filtering”
  2. go to the “URL” tab
  3. click on “Deny Sequence…”
  4. enter “/data/” in the popup box and click “OK”
  5. Repeat the “Deny Sequence…” instruction for the /conf/ /bin/ and /inc/ directories

In IIS 7

  1. select “IIS Request Filtering”
  2. go to the “URL” tab
  3. click on “Deny Sequence”
  4. enter “/data/” in the popup box

Note: By default, the Management Console snap-in for Internet Information Services 7 does not have UI access to “IIS Request Filtering” section. However, can be enabled by installing “IIS Administration pack 1.0” by using the Web Platform Installer.

Also note: Ensure you enter “/data/” and NOT just “/data”, otherwise pages that start with “data” will be inaccessible.

Alternatives for IIS 7+

If you can't access IIS configuration options (as in shared hosting sites), you can use one of the following methods

Alternative 1:

You can place the following file in your dokuwiki root:

<?xml version="1.0" encoding="UTF-8"?>
                    <add sequence="/data/" />
                    <add sequence="/conf/" />
                    <add sequence="/bin/" />
                    <add sequence="/inc/" />

Alternative 2:

You can put the following web.config file in the directories you have to protect.

  • data
  • conf
  • bin
  • inc (isn't dangerous when accessible, though)
<?xml version="1.0" encoding="UTF-8"?>
        <handlers accessPolicy="None" />

IIS 6.5 and below

  1. Open the configuration tool: Start → Settings → Control Panel → Administrative Tools → Internet Information Services
  2. Navigate to the directory you want to protect: Local Computer → Web Sites → Default Web Site → path to directory
  3. Right-Click the folder and chose Properties → Directory Security → IP address and domain name restrictions → Edit…
  4. Choose “By default, all computers will be: Denied access”
  5. Repeat this for /data/ /conf/ /bin/ and /inc/ directories

Deny Directory Access in Lighttpd

Using a URL re-write you can deny access to the above directories. In your lighttpd.conf file adding the following URL rewrite rule should be sufficient to keep people out1) . It suppose your Dokuwiki files are installed under http://yourwebsite.tld/dokuwiki/. Don't forget to uncomment “mod_rewrite” in the server.modules section.

url.rewrite-once = ( "^/dokuwiki/(data|conf|bin|inc)/+.*" => "/nonexistentfolder" )

Or use “mod_access”. More examples available here.

$HTTP["url"] =~ "^/dokuwiki/(data|conf|bin|inc)/+.*" {
    url.access-deny = ("")

Deny Directory Access in Nginx

Access to aforementioned directories can be disabled in DokuWiki server section of Nginx configuration file. In your nginx.conf file add the following location to prevent access to secure directories.

This instruction is slightly misleading. What you should actually edit is the /etc/nginx/sites-available/default file. Remember to first create a backup by issuing cp /etc/nginx/sites-available/default /etc/nginx/sites-available/default.bak Or in the virtualhost where you are hosting dokuwiki

    location ~ /(data|conf|bin|inc)/ {
      deny all;

Note: if you are using xsendfile, the above rules will break sendfile functionality. Consider the following:

    location ~ /(conf|bin|inc)/ {
        deny all;
    location ~ /data/ {

Deny Directory Access in Cherokee

It is relatively easy to forbid access to those directories using Cherokee. In cherokee-admin, select the virtual server where dokuwiki is installed and select rules management.

then add a new “Regular Expression” rule and put the following in it (supposing that dokuwiki sits on the root directory):


Remember to set it as “NON FINAL”, because if not, some code under those directories may still being executed under certain circumstances (“Extensions php” rule as “NON FINAL” present, for example).

Then go in “Handler” section and select HTTP Error. Finally select “403 Forbidden” in HTTP Error.

Deny Directory Access in Caddy

Here is an example Caddyfile for a wiki served with Caddy: {
        log /var/log/caddy/dokuwiki.log
        root /var/www/dokuwiki/
        # Assuming install/config of php-fpm 
        # to listen on localhost:9000
        fastcgi / php
        # This block below sends an HTTP 401 message when
        # a client attempts to access the secured directories. 
	status 401 {

Rename data Directory

Securing the data directory is most important. If you cannot move directories out of the webserver (see below) or can't configure your webserver to deny access (see above), then you should at least make it harder to guess the name of your data directory.

To do so, rename your data directory to something cryptic (eg. a long row of letters and numbers) and reconfigure your savedir option in your conf/local.php file.

Move Directories out of DocRoot

The most secure way to avoid any access to the mentioned directories is to move them outside the so called “Document Root” of your Webserver.

WARNING: If you are planning to use the installer, you need to install your wiki executing the install.php script first before you can do this step. If the Move Directories operation is done before, the installer execution will fail.

data Directory

  1. Move the data directory (and all its contents) out of the document root
  2. Edit the savedir setting to point to the new location of the data directory.

For example, if the data directory is moved to /home/yourname/data, add the following line to conf/local.php:

$conf['savedir'] = '/home/yourname/data';

conf Directory

  1. Move the conf directory (and all its contents) out of the document root
  2. Create a file named preload.php inside the inc directory and set the DOKU_CONF define to the new location of the conf directory.

For example, if the conf directory is moved to /home/yourname/conf, create the following inc/preload.php:

// DO NOT use a closing php tag. This causes a problem with the feeds,
// among other things. For more information on this issue, please see:w

bin Directory

The bin directory contains CLI tools. If you don't have shell access on your server anyway you can simply delete the directory and its contents. Otherwise just move it out of the document root. No further configuration needed.

inc Directory

There is currently no easy way to move this directory out of the document root. But since it doesn't contain any sensitive data it isn't worth the effort to try anyway.

DokuWiki Configuration Settings

DokuWiki contains several configuration settings that have an impact on various security aspects of the installation. Please refer to the documentation of each setting to learn what they do and what suggested settings are.

  • allowdebug – disabling debugging output to avoid system information leakage :!:
  • fmode, dmode – set the file permissions of DokuWiki created files, also read info on setting up permissions
  • fetchsize – configure caching of external data
  • fullpath – showing full path names for pages
  • usewordblock – prevent spam through a blacklist
  • mailguard – avoid mail address harvesting robots
  • iexssprotect – protect against a XSS problem within Internet Explorer
  • htmlok – enable HTML
  • phpok – enable PHP
  • hidepages – hide certain pages from indexes and search
  • safemodehack – work around safe mode restrictions
  • disableactions – disable certain actions, e.g. registration or view source
  • baseurl – set a fixed server name the wiki should use to avoid server name spoofing attacks

Plugin Security

DokuWiki has lots of community contributed plugins. Plugins add new functionality to DokuWiki by adding new code. This means the code has practically any access to your server. Additionally plugins are distributed separately from DokuWiki in an entirely ad-hoc manner. They are not subject to the same degree of attention and review that the core DokuWiki code base gets. So security precautions are necessary before installing a plugin.

Here are some tips to help you with choosing the plugins you install.

  • If you can, review the plugin source code yourself, before installing it.
  • If in doubt, ask on the mailing list.
  • Plugins are installed under the DokuWiki lib directory, which is directly accessible from the outside. Review what a plugin contains and lock down access with .htaccess files as appropriate.
  • Plugins are authored by developers not directly related to the DokuWiki project - they may be inexperienced, have malicious intent or may host the plugin source code on a server that has been compromised. Be careful whom you trust!
  • Review the plugin page for mentioned security warnings and upgrade the plugin when new releases become available.

See also: How to report security issues in plugins

Access Control

With Access Control Lists (ACL) you can restrict which pages and/or namespaces users have access to. You can give read and write permissions depending on the user group or single users.

Additional Reading

Unfortunately it does not not when people are using Vivaldi and probably other chromium based browsers. When combined with “mod_access” it does keep people out.
security.txt · Last modified: 2017-07-08 02:01 by