Incorrect rendering of Category-Page (edit-tags.php?taxonomy=category), any action (edit, delete, new) results in 403 Forbidden Error

[leanderbraunschweig]

/edit-tags.php works normally, once I enter a page with the following ?taxonomy, the page breaks; first with the CSS (not loading, no styles, see image attached), then I get a 403 Forbidden error once I try to edit/delete/add a category.

Console Output (Errors/Advice):

[15:53:25.599] GET http://www.allcontainer.de/wp-admin/edit-tags.php?taxonomy=category [HTTP/1.1 200 OK 300ms]

[15:53:26.099] Mutations-Ereignisse sollten nicht mehr verwendet werden. Verwenden Sie MutationOberver stattdessen. @ chrome://firebug/content/chrome/tabContext.js:589

[15:53:26.482] GET http://www.allcontainer.de/wp-admin/css/colors-fresh.css?ver=3.4.2 [HTTP/1.1 403 Forbidden 45ms]

Array of CSS-related errors following, 2 excerpts:

[15:53:26.339] Fehler beim Verarbeiten des Wertes für 'background-image'.  Deklaration ignoriert. @ http://www.allcontainer.de/wp-admin/load-styles.php?c=0&dir=ltr&load=admin-bar,wp-admin&ver=3.4.2:1
[15:53:26.339] Farbe erwartet, aber 'bottom' gefunden.  Fehler beim Verarbeiten des Wertes für 'background-image'.  Deklaration ignoriert. @ http://www.allcontainer.de/wp-admin/load-styles.php?c=0&dir=ltr&load=admin-bar,wp-admin&ver=3.4.2:1

[...]

[15:53:26.787] getAttributeNode() sollte nicht mehr verwendet werden. Verwenden Sie stattdessen getAttribute(). @ http://www.allcontainer.de/wp-admin/load-scripts.php?c=0&load=jquery,utils&ver=3.4.2:2

[15:53:26.787] Das angegebene Attribut auf Attributen sollte nicht mehr verwendet werden. Es liefert immer true. @ http://www.allcontainer.de/wp-admin/load-scripts.php?c=0&load=jquery,utils&ver=3.4.2:2

Log when trying to edit/delete/add returns a simple 403:

--
[16:08:07.317] POST http://www.allcontainer.de/wp-admin/admin-ajax.php [HTTP/1.1 403 Forbidden 79ms]

Files are accessible directly (f.ex. the stylesheet)...

I have encountered this behaviour before on a different server / within a different site with regards to the widget-panel – there I found a workaround via "activate accessability-mode" (or similar wording). Now I can go by via directly editing the MySQL-entries but this is not suitable really.

---

## All plugins deactivates, standard theme in action, newest WordPress-version installed.

## Search for "taxonomy 403 forbidden" did not return any results

## Same output with different browsers (tested: Firefox, Safari)

Some server details:

OS/Server - Linux proa 2.6.32-23-server #37-Ubuntu SMP Fri Jun 11 09:11:11 UTC 2010 x86_64
PHP Version – 5.3.2-1ubuntu4.17
Loaded Extensions – Core, date, ereg, libxml, openssl, pcre, zlib, bcmath, bz2, calendar, ctype, dba, dom, hash, fileinfo, filter, ftp, gettext, session, iconv, json, mbstring, SPL, standard, posix, Reflection, Phar, shmop, SimpleXML, soap, sockets, exif, sysvmsg, sysvsem, sysvshm, tokenizer, wddx, xml, xmlreader, xmlwriter, zip, cgi-fcgi, ADOdb, curl, ffmpeg, gd, imagick, intl, mcrypt, mysql, mysqli, PDO, pdo_mysql, mhash
MySQL – 5.1.63-0ubuntu0.10.04.1

If any more info is needed, I'll be hapy to assist/comply. Thanks in advance for your efforts.

Regards!

[leanderbraunschweig]

Cannot include steps to reproduce (don't know...) but may be able to grant backend-access in order to test/debug.

[miqrogroove]

leanderbraunschweig, what exactly is the WordPress bug that you are reporting?

If you are experiencing 403 errors on CSS files, we can't help you with that here. That is a web server issue.

[leanderbraunschweig]

Thanks for getting back.

Seems I should be looking into a mod_security issue, which doesn't allow or process the query string commands properly.

Sorry for taking up your time, I went ahead and closed it.