XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk
  1. Board index / 
  2. XOOPS Community Support forums / 
  3. Beginner's Corner 
  4.  / Xoops site hacked - beware!
Register
11
Anonymous
Re: Xoops site hacked - beware!

  • 2008/3/28 10:25

  • Anonymous

  • Posts: 0

  • Since:


@propaed

You need to update a lot of stuff on your site, including XOOPS itself. Many updates and bug-fixes are security-related.

Start the updates with XOOPS (you can use the full download to update to 2.0.18.1) and then update those modules that use "spaw" editor. You might want to replace them altogether.

And has been said before, get Protector from GIJOE's site - in my view it's a "must have" module and it's always the first one I install on a new site.
12
McDonald
Re: Xoops site hacked - beware!

  • 2008/3/28 10:50

  • McDonald

  • Home away from home

  • Posts: 1072

  • Since: 2005/8/15


A handy tool to check if your website contains vulnerabilities is Acunetix Web Vulnerability Scanner.
You can use it for your prod. website but better to do it on a local server (XAMMP or WAMP or equal).
Scanning might take a while but it's worth it.

You can download the free edition (Windows only) here after registration: http://www.acunetix.com/cross-site-scripting/scanner.htm

With this tool some vulnerabilities have been found (and fixed).

Resized Image
13
maketravel
Re: Xoops site hacked - beware!

  • 2008/3/28 11:04

  • maketravel

  • Just popping in

  • Posts: 35

  • Since: 2008/3/20


please update your XOOPS protector!

Xoops Protector 3.04a stable
14
Yurdal
Re: Xoops site hacked - beware!

  • 2008/3/28 11:15

  • Yurdal

  • Friend of XOOPS

  • Posts: 386

  • Since: 2005/3/27


Hmm latest protector is 3.16 right ?
15
Anonymous
Re: Xoops site hacked - beware!

  • 2008/3/28 11:29

  • Anonymous

  • Posts: 0

  • Since:


Quote:
Yurdal wrote:

Hmm latest protector is 3.16 right ?


Yes, but that is marked as a beta version.

It's a matter of personal choice. I use v3.16beta and it seems fine to me. I know others think the same.

I wouldn't normally use a beta-version of a module on a production site but in this case I made an exception on the grounds that GIJOE is an excellent coder and the authority on XOOPS and security. He wouldn't have released something that he wasn't happy with even if it is marked as beta. In short, I took the source into account
16
migrieren
Re: Xoops site hacked - beware!

  • 2008/3/28 11:30

  • migrieren

  • Just popping in

  • Posts: 6

  • Since: 2008/3/28


hmm, i think the latest stable version is 3.04a and the latest beta version is 3.16.

regards
17
musashi74
Re: Xoops site hacked - beware!

  • 2008/3/28 13:51

  • musashi74

  • Just popping in

  • Posts: 18

  • Since: 2005/2/15


Thanks for the advice guys - I dumped TinyEvent and will be upgrading Protector ASAP. If anyone can describe vulnerabilites with xcGallery, it would be appreciated as well..

[edit]
Moderated by JAVesey

Sorry - you might not be malicious but someone who reads it might be.

We've had a lot of trouble with this site being hacked - wouldn't want to encourage them to have a go at us, eh?[/edit]
18
Anonymous
Re: Xoops site hacked - beware!

  • 2008/3/28 14:10

  • Anonymous

  • Posts: 0

  • Since:


@musashi74

Thanks for the advice - very interesting. Sorry, but I felt compelled to moderate the last bit.

As for xcgal - yeah, I'd like to know too. It's such a good and widely used module that we should, as a community, ensure that it's kept up to date. I'm willing to learn and give it a go..... anyone want to join me?
19
musashi74
Re: Xoops site hacked - beware!

  • 2008/3/28 14:33

  • musashi74

  • Just popping in

  • Posts: 18

  • Since: 2005/2/15


JAVesey

No problem - I understand (and I'm pretty sure anyone capable of using that info can figure it out more quickly than I did...)
20
propaed
Re: Xoops site hacked - beware!

  • 2008/4/5 23:11

  • propaed

  • Just popping in

  • Posts: 3

  • Since: 2008/3/28


As said earlier, reset to uninfected backup. Waited.
Next day, got infected again.
Reset to backup and disabled TinyEvent. Waited.
Nothing happend since then.
Imho, count TE as the vulnerability in this cases.

Updates are really necessary. Thanks for advice, esp. about Protector.
« 1 (2) 3 »

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

312 user(s) are online (257 user(s) are browsing Support Forums)

Members: 0

Guests: 312

more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Nov 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits