Serendipity 2.0.4 and 2.1-beta2 released

Serendipity 2.0.4 is a maintenance security release which addresses these issues:

  • [Security] Prevent moving files by using their directory name.
    [Security] Possible SQL injection for entry category assignment
    [Security] Possible SQL injection for removing&adding a plugin

    All issues require a valid backend login.
    Thanks to Hendrik Buchwald for finding this via their
    RIPS source code analyzer (
  • [Security] Add new configuration option to enable fetching local files for the media uploader. By default this is now disabled to prevent Server Side Request Forgery (SSRF). Thanks to Xu Yue for pointing this out!

Alongside a new Serendipity 2.1-beta2 version has been released, with the same fixes plus some more progress on the road to the 2.1 release. Features like these have been added:

  • New API wrapper for URL downloads that plugins can use (serendipity_request_url)
  • Added new Theme "Skeleton" (responsive, mobile first)
  • Improved preview iframe handling
  • Changes (simplifications) in template file routing for backend/frontend views, new smarty {getFile} function for theme authors

Simply upgrade by unpacking and uploading the release file and confirming our web-based upgrader.


Trackback specific URI for this entry


Display comments as (Linear | Threaded)

-thh on at :

Thanks for your hard work!

Two small nitpicks:

  1. The "Development state" on the blog sidebar should be updated from "Recommendation(s): Use 2.0.3 release" to 2.0.4

  2. The relase notes on GitHub at don't have a MD5 checksum, so the auto updater will fail.

artodeto on at :

Hey s9y team,

I've scribbled a small script [0]. Just write me a mail if this is something I can polish and if you want to use it as repository in your github group [1]. I would also like to be the developer for this.



artodeto on at :

Hey s9y team,

I've polished my script [0]. I've upgrade three installations right now.



Add Comment

E-Mail addresses will not be displayed and will only be used for E-Mail notifications.

To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly.

BBCode format allowed
Markdown format allowed