• Resolved mywebdesign

    (@mhwebdesign)


    Hi there,

    Not a support question but rather a query.

    WP Source code tends to give out way too much information. It’s easy for someone to lookup source code and then click a link (even if there is a rewrite in place). If that direct link is to a JS/CSS/PHP file required to run the site, then the client/end user will have access to the contents of that file.

    This often gives hackers a heads up as to plugins and scripts installed.

    How worried about such a vulnerability should I be?

    I mean once someone is able to determine themes and plugins/scripts we are using, it’s just a matter of them finding a way to exploit them.

    Even hiding wp-admin/wp-login, it just masks a problem rather than resolving it, as once the new name is worked out they can hit that.

    I realise that nothing is 100% fool proof… but how does AIO face such issues (like code snooping)?

    Thanks πŸ™‚

Viewing 11 replies - 1 through 11 (of 11 total)
  • Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    You’re missing the whole point about collaboration with open source code.

    WP Source code tends to give out way too much information.

    It really doesn’t and never has. Open source does not mean insecure by default. Code is secure or insecure regardless of whether or not you can actually read the code.

    Additionally having that code available means that more people can and do provide updates to improve it.

    Limiting factors (like time and resources) often mean we need to prioritize.
    While many of us would prefer restricting access to our code, to prevent bad actors from trying to find loopholes, Open Source regularly allows millions of people to build sites at a speed they would never have been able to, relying only on their own knowledge and what they can afford to buy.
    Furthermore, relying solely or primarily on security through obscurity, is not a very effective strategy, while there are other ways to mitigate (although not eliminate) the security risks that come with not having a “black box” so to speak.

    Thread Starter mywebdesign

    (@mhwebdesign)

    I understand the benefits of open source software and collaboration, and about the concept of more eyes = more solutions, but that doesn’t absolve potential risks created with highly visible code.

    Hence my query of this software package (and another).

    I’m keen to know what steps AIO (and others) can take to mitigate this very real risk.

    I don’t mind having visible code, but when hitting a .JS or .PHP or .CSS file leaks versioning information, or specifics, it can create a larger attack vector for a nefarious character.

    Hence limiting that attack vector size is important (at least to me).

    I’d rather spend a short amount of time picking the best plugin for the job, and locking a site down, than several hours restoring a backup and recovering from a malware/injection attack because my code let something out it shouldn’t have.

    Hope that explains it better.

    Neither Jan nor myself are associated with this plugin or its authors.

    We also cannot give recommendations for alternative plugins in any particular plugin’s support forum or in their reviews – because that isn’t cool.

    As such, there isn’t much that we can offer in the ways of productive discussion on this thread that has not already been said.

    All the best πŸ™‚

    Thread Starter mywebdesign

    (@mhwebdesign)

    All good πŸ™‚ That’s why I triggered the discussion on two different plugins forums πŸ™‚

    Plugin Contributor mbrsolution

    (@mbrsolution)

    @mhwebdesign, someone asked a similar question a while back regarding the source code. Unfortunately there is no feature available in our plugin to hide the browser source code. Also, as far as I know there are no future plans to implement such a feature in our plugin.

    If you require any more help or information, please let me know.

    Kind regards

    Thread Starter mywebdesign

    (@mhwebdesign)

    Hi MBRSolution,

    Thanks for your reply.

    I guess if millions of websites out there have their code exposed, as long as the plugin is helping to shut the door of anyone that might have a look, that’s the main thing.

    Can the plugin be used to monitor access to specific directories?

    Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi,

    Can the plugin be used to monitor access to specific directories?

    The File Change Detection scanner can be used to monitor any changes to files and folders in your site. Is this what you are looking for?

    Thank you

    Thread Starter mywebdesign

    (@mhwebdesign)

    That should assist part of the way.

    It was more to log if someone was directly trying to load a .css/.js file, or something (in other words direct loading files to look for vulnerabilities).

    Or if they attempt to directly access /wp-admin, /wp-content, or /wp-includes.

    Whilst one can block off / obfuscate access to those directories, it would be nice to be alerted to if anyone is attempting to access those directories (or files within them).

    Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi,

    It was more to log if someone was directly trying to load a .css/.js file, or something (in other words direct loading files to look for vulnerabilities).

    Or if they attempt to directly access /wp-admin, /wp-content, or /wp-includes.

    The only way someone can upload a file in your site is by having access to your site. The Brute Force features in our plugin will prevent this from happening. The other way they can access your site is by hacking the server. Which I am sure your server administrator already has security measures set in place.

    Whilst one can block off / obfuscate access to those directories, it would be nice to be alerted to if anyone is attempting to access those directories (or files within them).

    Currently we don’t have any feature in our plugin that can warn you if someone is accessing your site forcefully. However the security features already available in our plugin will prevent anyone from accessing your site without permission.

    Kind regards

    • This reply was modified 6 years, 2 months ago by mbrsolution.
    Thread Starter mywebdesign

    (@mhwebdesign)

    Thanks mbrsolution.

    Will have a look into it. Might have to look at auditing plugins and see if perhaps they offer that side of functionality.

Viewing 11 replies - 1 through 11 (of 11 total)

The topic ‘Code snooping and exploitation on WP’ is closed to new replies.