NeoBill CMS v0.8 Alpha - Multiple Web Vulnerabilities
Common Vulnerability Scoring System:
NeoBill is a web-based Customer Management and Billing solution designed for web hosting providers,
particularly hosting resellers. It is developed in PHP, uses MySQL as the backend database, and
is licensed under the GPL. The script supports independent payment gateways, and registrars of domain names.
Key features of the product:
* Open source (GPL)
* Support for PHP4 and PHP5
* Use MySQL database
* Independent Payment Gateways Module
* Indepenent Domain Registrar Module
* Multi-user system
* The ability to integrate third-party modules
* Using Smarty templates
* Checking the active, inactive and pending accounts
* Attachments to the memos Account
* Sending predefined e-
ov for new customers
* Creating and editing accounts, which can be printed or sent by mail to its customers
* Accounts can be generated by one or all at once
* Set one-time and monthly payments for each service / service
* Services have a duration of 1,3,6 and 12 months
* Domain registration through API Directi
(Copy of the Vendor Homepage: http://www.neobill.net/ )
The Vulnerability Laboratory Research Team discovered multiple web vulnerabilities in the NeoBill v0.8 Alpha Content Management System.
2012-08-19: Public or Non-Public Disclosure
A persistent input validation vulnerability is detected in the NeoBill v0.8 Alpha Content Management System.
The vulnerability allows remote attackers or local low privileged user account to inject/implement malicious persistent script
code on application side of the neobill v0.8 web application. The vulnerability is located in the user account module with
the bound vulnerable contactname or username parameters. Attackers can inject via register account or update profile malicious
persistent script codes as companyname and username. The code will be persistent executed in the administration backend when processing
to watching the user account listings. Successful exploitation of the vulnerability result in persistent session hijacking attacks,
persistent phishing requests & stable persistent module context manipulation.
[+] User Accounts - Management [Admin Backend]
Multiple client side cross site scripting vulnerabilities are detected in the NeoBill v0.8 Alpha Content Management System.
The vulnerability allows an remote attacker to manipulate client side application requests with medium or high required user
inter action. The vulnerabilities are located in the unsanitized output of the Uncaught SWException & Invalid Object Exception
web application modules. Successful exploitation of the vulnerability result in client side session hijacking, non-persistent
phishing requests & non-persistent module context manipulation.
[+] 2 x Exception Handling
[+] Uncaught SWException Handling
[+] Invalid Object Exception Handling
Proof of Concept:
The persistent web vulnerability can be exploited by remote attacker with low privileged application user account and low
required user inter action. For demonstration or reproduce ...
Review: Listing - Contactname & Username
admin admin "><[PERSISTET INJECTED SCRIPT CODE!]")' <="" td="">
href="mailto:[email protected]">[email protected]
Affected User Account - Listing:
The non persistent cross site scripting vulnerabilities can be exploited by remote attackers without low privileged application
user account with medium or high required user inter action. For demonstration or reproduce ...
Exception Handling - Uncaught SWException & Invalid Object Exception
New Domain Service:
The security risk of the persistent input validation vulnerability is estimated as high.
The security risk of the non persistent cross site scripting vulnerabilities are estimated as low(+)|(-)medium.
Vulnerability Laboratory [Research Team] - Benjamin Kunz Mejri ([email protected])
The information provided in this advisory is provided as it is without any warranty. Vulnerability-Lab disclaims all warranties,
either expressed or implied, including the warranties of merchantability and capability for a particular purpose. Vulnerability-
Lab or its suppliers are not liable in any case of damage, including direct, indirect, incidental, consequential loss of business
profits or special damages, even if Vulnerability-Lab or its suppliers have been advised of the possibility of such damages. Some
states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation
may not apply. We do not approve or encourage anybody to break any vendor licenses, policies, deface websites, hack into databases
or trade with fraud/stolen material.
Domains: www.vulnerability-lab.com - www.vuln-lab.com - www.vulnerability-lab.com/register
Contact: [email protected] - [email protected] - [email protected]
Section: video.vulnerability-lab.com - forum.vulnerability-lab.com - news.vulnerability-lab.com
Social: twitter.com/#!/vuln_lab - facebook.com/VulnerabilityLab - youtube.com/user/vulnerability0lab
Feeds: vulnerability-lab.com/rss/rss.php - vulnerability-lab.com/rss/rss_upcoming.php - vulnerability-lab.com/rss/rss_news.php
Any modified copy or reproduction, including partially usages, of this file requires authorization from Vulnerability Laboratory.
Permission to electronically redistribute this alert in its unmodified form is granted. All other rights, including the use of other
media, are reserved by Vulnerability-Lab Research Team or its suppliers. All pictures, texts, advisories, sourcecode, videos and
other information on this website is trademark of vulnerability-lab team & the specific authors or managers. To record, list (feed),
modify, use or edit our material contact ([email protected] or [email protected]) to get a permission.
Copyright © 2012 | Vulnerability Laboratory
-- VULNERABILITY RESEARCH LABORATORY LABORATORY RESEARCH TEAM CONTACT: [email protected]