Joomla : social engineering content detected - joomla

Google is saying I have a social engineering content in my joomla 3 web site. This is the URL
plombier-chauffagistes[DOT]fr/ppp/79629b8a3ff4b34eb8db788c68d680ce/login.php?cmd=_login-run&dispatch=5885d80a13c0db1f1ff80d546411d7f8a8350c132bc41e0934cfc023d4e8f9e5
You can try to open this URL in google chrome : it will display an error :(
I can't fix the problem : the "ppp" folder does not exists, I made some rewrite rules in .htaccess, I also tried to delete .htaccess, but the problem still remains.

The first thing that you need to do when this thing happens is check the .htaccess file, which is most likely hacked.
The second thing would be to just overwrite your core Joomla files from those from a fresh Joomla install.
If you still have the problem, please post back here.

Related

The requested page can't be found

I'm a new beginner to Joomla. I'm trying to build a website with a sub domain of joomla (free sub domain). After successfully setting up and installing the database plus other components according to several beginners' tutorials, where I successfully upload several templates, I try to test the link of my website but all I get is this error message:
The requested page can't be found.
An error has occurred while processing your request.
You may not be able to visit this page because of:
an out-of-date bookmark/favourite
a mistyped address
a search engine that has an out-of-date listing for this site
you have no access to this page
Search
You may wish to search the site or visit the home page.
Search ...
Search ...
Home Page
If difficulties persist, please contact the System Administrator of this site and report the error below.
404 Article not found
How can I really go about solving this issue because after intensive research I have found out that this error message is very common for beginners when it comes to Joomla.
Some Suggestions:
SEF URLS
Try using a non-SEF URL to access an article to see if that works.
For example, check in Content -> Articles for a valid published article ID (the article IDs are in the last column at the right hand side of the page) and access the page using a URL like this:
http://[your-domain-name].com/index.php?option=com_content&view=article&id=xx
where xx is the article ID.
If this works, then your problem has something to do with SEF URLs or URL Rewriting.
You can temporarily disable SEF URLs and URL Rewriting in the Global Configuration.
.htaccess
A badly configured .htaccess file could cause this issue.
Assuming the .htaccess file exists in the root folder of your website (e.g. in the /public_html folder) then try copying .htaccess to .htaccess.old as a backup and reset the .htaccess file to the default settings by copying htaccess.txt to .htaccess.
htaccess.txt should also be found in the root folder of your website as part of a normal Joomla install.
Test whether this fixes the issue.
Third Party Extensions
Try disabling any SEF related third party extensions.

Magento Connect Manager redirecting to 3rd party site - malicious code?

I have a strange problem with Magento Connect Manager: firstly, if I cliick the "settings" tab, the page redirects to an the 1and1.com.com homepage with an affiliate link suffix (1and1 arent my hosting provider).
Similarly, if I try and uninstall / reinstall any extension on the "extensions" page, the same 1and1.com page appears in the window below the list of extensions (where you would normally see the installation being actioned).
I am also unable to install any new extensions / or uninstall any existing ones. I'm guessing this is the result of some malicious code being inserted somewhere?
does anyone else have any similar experience or any idea how to fix?
Thanks in advance.
Rollback your updated htaccess to default magento htaccess and clear your cache and test again.
OR
In your current htaccess file you may find some urls like
http://www.yourdomain.com/
update them to your website url.

How do i fix these wrong URL's in my broken magento deployment?

This is my first attempt at using Magento to develop a site. I have to admit the learning curve has been steep, but i have been able to navigate most of the challenges thus far. Here at the final hurdle, however, i have stumbled.
Specs:
Magento 1.7.0.2
Apache version 2.2.22
PHP version 5.3.10
MySQL version 5.1.65-cll
Magento is located in a folder on the server named magento one directory down, as in http://www.mydomain.co.za/magento
Problem:
No images are displayed in the front end or backend. It is as if it cannot access the stylesheets. When viewing the source, i can see that the paths are wrong. It searches for the stylesheets in http://www.mydomain.co.za/ and not in the magento folder. I can access the backend by typing in http://www.mydomain.co.za/magento/index.php/admin and that brings up the backend without any styling. After that however, every request results in 404. The URL looks like http://www.mydomain.co.za/magento/adminindex.php without a slash between admin and index. Introducing that slash manually after every 404 results in correct page being displayed (still without styling). So clearly the problem is here, but i can't seem to fix it. And YES, i do have the slash after the path in the database for both secure and unsecure.
Attempts to solve:
Changed the url’s in database link
Changed app/etc/local.xml to use correct database
Changed .htaccess to include this line: RewriteBase /magento/ (but i
removed it again)
Deleted the appropriate cache and sessions folders
Tried some of the suggestion given here link
Now, i am stuck. I have worked my way through error upon error (no fault of Magento, just the learning curve) and i am tired… :-( If someone can please give me some advice as to what to try next, it would be greatly appreciated.
I found these links of the (seemingly) similar problem. Clearly there is something happening here. The other thread never solved the issued, just found a work around. Is it possible that we have run into a bug? Something is stripping that slash out and it isn’t any of the usual suspects… dum dum dum
link
link

CodeIgniter installation questions

When I upload the CodeIgniter package to my web server on Bluehost, I can get into the main page, but not sure if this is all I have to do.
I've read many questions here about the same issue, but nothing worked for me. As I understand that I have to add some code .htaccess codeignitor code to the root .htaccess, but that made a mess in my url redirection.
I verified that mod_rewrite is working fine through some php code, but still unsure about the installation procedure. did any have this framework works on his Bluehost webserver??
I found the installation guide on this site, but the test fails back to 404 page.
By the way, I uploaded the package on a subdomain folder
Any comments are appreciated.
That's nothing wrong with Bluehost.. I've upload my CI into a subdomain folder in Bluehost. and nothing wrong.. It work perfectly..
Some questions :
Do you set your base_url correctly? or you can leave it blank.
Are you sure you've write the right .htaccess, and put it in the right place? make sure the index page in the config file is blank.

Cannot upload images when WordPress is sat on a virtual host configuration

This is my first post to this Forum, please forgive me if this has been answered elsewhere--I did search and was unable to find an answer to my particular problem, so any help would be greatly appreciated.
I am working on a WP site for a client who wants to upload images to new posts (who doesn't hey?). In setting up the site I have done the following:
1) Enabled File Upload by CHMOD default dir to 777.
2) Changed max file size.
3) Changed allowed filetypes to include necessary file types.
When I try to upload anything I get the following error:
“Bobst Expertfold 80 110 (Dec 2010).jpg” has failed to upload due to an error
The uploaded file could not be moved to /var/www/vhosts/glossopcartons.com/httpdocs/wp-content/uploads/2010/12.
The above error mentions 'glossopcartons.com', this WP site is actually sat on glossopcartons.co.uk. It's obvious that there is some kind of virtual host configuration going on and the image is trying to be uploaded to a folder on a different domain (glossopcartons.com instead of glossopcartons.co.uk).
I don't manage the hosting, I have just been assigned with the build. However, I have access to the plesk cpanel but I dont know what I need to do?
Does anyone know what is causing this problem? The site has actually been made live and this issue has been spotted after the launch(everything worked fine on the test server), and I am scratching my head trying to figure it out.
Is there something I can put in my wp-config.php or .htaccess file to tell WP to upload to a different location.
Any help would be greatly appreciated.
Dan
First thing is 777 permisions are too loose and will get you hacked; they should be no more than 755. Hardening WordPress « WordPress Codex
For the difference in URLs: that sounds like a DNS or virtual host config, but try adding the full URL path in Settings>>Media Settings. Might not work.
Why are there sites at both domains? Why not domain forward glossopcartons.com to glossopcartons.co.uk?
Make sure PHP lets you upload files larger than what you are trying to upload.
Experienced the same problem on several old sites. This problem occurs sporadically and is not commonly occuring on other websites on the same server
Try going to your "Media Settings" page... do you see a "Store uploads in this folder" option with a long path to your uploads folder? If so... this is your problem... WordPress 3.5+ does not seem to require this long path, but more of a site relative path (which is great!)
Change your "Store uploads in this folder" to "wp-content/uploads"... when you "save settings" you should see that field disapear entirely, never to bother us again ;-)
This occured for me when my hosting provider changed the folder structure on the server making this long URL incorrect. Therefore WordPress could not find the "uploads" directory at all.
Hope that helps...
Here's some things you might want to check in case your still having problems...
Update to WordPress 3.5 +
Update all plugins
Check file permissions 755 on the uploads dir/
Check PHP version

Resources