I just stumbled over this log entry:
Location http://example.com/user/register
Message Incorrect CAPTCHA
Data:
session_id = ''
captcha_result = '...'
author_ip = '...'
author_id = '51347'
author_name = 'some-username'
author_mail = 'some-mailaddress'
Obviously, someone submitting the user_register form can never have an author_id already.
No idea why the code tries to look up an existing account for author_name, but I can only guess this must have been wrongly migrated from old code in the original patch that introduced the form value mapping.
This is not a security issue. It only affects Mollom's spam analysis performance and is quite unfortunate, to say the least.
Comments
Comment #1
sunForgot to copy one comment.
Comment #3
dries commentedMmm, yeah. Good catch. Not sure why the tests failed but we should get this committed once green.
Comment #4
sunThis patch will pass tests as soon as #1198192: "field_xyz][0][value" sometimes contained in post_body sent to Mollom has landed.
Comment #5
killua99 commentedWe should change this lines in mollon.module
to this
We did this change and is working very well. I post this same issue
#1238060: user_load through 'name' is a good practice?because in my search didn't show me this topic.Sorry for the duplicate content.
I'm impresive that this kind of module that have 30296+ sites in use, didn't fix this bug ASAP.
Comment #6
rodricels commented#1: mollom.author-mapping.1.patch queued for re-testing.
Comment #7
rodricels commentedThe patch are green now! (well, since august...).
I use it on some production sites without problems, it can be reviewed by someone more?
Comment #8
sunRe-rolled against 7.x-2.x.
Comment #9
sunThis looks ready to fly for me.
Comment #10
sunCommitted and pushed to 7.x-2.x.
Comment #11
sunMerged into 6.x-2.x via #1379136: Backport recent changes in 7.x-2.x.