One of the requirements to get your vulnerable extension marked as resolved is that you publish a security release announcement on your website. However we have noticed that developers often seem to have trouble with understanding what this means.
So what does it mean? We do not have a standard format for this, however we do ask that any reasonably...
Recently an issue was reported to the Vulnerable Extensions List team, which affected the blogging platform for Joomla, Easy Blog. After some thought we decided that it did not fall within the normal definition of a security issue that would merit listing on the VEL. It was reported to us by a site owner whose site had been hit by an...
There has a been a lot of talk recently about responsible disclosure issues especially with new developers and glory seekers. The VEL team have its own responsible disclosure code, namely that we wont list any Proof of concept or samples. we will only give the bare minimum.. All we ask is...
Following a community member suggestion obtaining a VEL website API, Phil Taylor from Blue Flame IT donated his API/JSON script for the community use.
It is available at http://vel.myjoomla.io/ however the docs have yet to be written.
{jb_quote} This JSON is provided for free, dont abuse this by hammering it with massive of calls please. The...
Right now there’s no machine-readable output format of the vulnerable extensions list. This causes a lot of issues when someone tries to find out, if a specific extension is listed on the VEL or not, because he or she wants to do for example one of the following things:
develop a plugin that automatically sends an email to the site...
If a person follows these few simple rules the majority of site hacks will not happen.
1.) Use a decent hosting provider. Cheap is not necessarily bad, and expensive is not necessarily good. Do your research. Take a few minutes to search for and read comments and reviews left by other users.
2.) If you don't need it for your sites functionality...