Pritlog v0.821 CMS XSS Vulnerability

ID 1337DAY-ID-18160
Type zdt
Reporter Benjamin K.M.
Modified 2012-04-29T00:00:00


Exploit for php platform in category web applications

Pritlog v0.821 CMS - Multiple Web Vulnerabilities

PRITLOG is an extremely simple, small (< 500K uncompressed) and powerful blog system. It does not use or need
a MYSQL database and fully works based on Sqlite. Sqlite is very similar to flat files and does not need any
server setup and comes as default with most PHP5 installations. Just drop Pritlog into your server and it
starts running. No separate installation is required.

* WYSIWYG editor - nicEdit
* Admin interface (change site properties, add authors, change password)\\\\\\\'\\\\\\\'\\\\\\\'
* Easy translation. Language selection available in the admin panel. Language files must be created.
* Sticky Posts
* Integrated login system with registration
* Pretty Urls
* SEO Optimization
* Page functionality for static pages
* Social Bookmarking widget: to enable easy sharing of post/blog
* Bbcode by editing html (work around)
* RSS Feeds
* Additional authors can be added by the admin
* Post Options w/ Teaser + Full Story (using *readmore* in the post)
* Ability to enable / disable comments per post * Global privacy option
* Ajax and jQuery for better user experience
* Post auto-save feature<
* Category cloud
* Theme engine for easy theme creation
* Plugins to easily add functionality

(Copy of the Vendor Homepage: )

The Vulnerability Laboratory Research Team discovered multiple Web Vulnerabilities in Pritlog v0.821 Content Management System.

Multiple persistent input validation vulnerabilities are detected in the Pritlog v0.821 Content Management System. The
allow remote attackers to implement/inject malicious script code on the application side (persistent). Successful
of the vulnerability can lead to session hijacking (manager/admin) or stable (persistent) context manipulation.
Exploitation requires
low user inter action. Attackers can inject malicious strings as author name to execute them when an admin is
processing to preview, review
or manage the listing of users. The bug is located on application side & the execution is persistent out of the user

management web
application context.

Proof of Concept:
The vulnerability can be exploited by remote attackers with low required user inter action. For demonstration or
reproduce ..


<legend>Manage Authors</legend>
<tbody><tr><td><strong>Author: </strong>"><iframe src="a"
onload='alert("vl")' <<br=""><br></td>
<td><label for="authorEmail">Email</label><br>
<input type="text" name="authorEmail" id="authorEmail" value="fufu () aol

# [2018-01-09]  #