The latest security release addresses this issue, yes. We've been in contact with the firm that released this and they coordinated with us to get the security release out before they announced it.
@50sQuiff said:
Thank you sir. Can you tell us which change was directed at this issue? I just want to be sure that no plugins expose the same vulnerability.
H00j
✭
Answers
I believe so.
For more details, check out the latest security update.
Yes that is why there is an update to 2.0.18.8 please upgrade
who reads announcements? they are almost as bad as reading documentation.
but then again - the announcement doesn't explicitly say it relates to the same issue.
I read the announcement and I already updated I was double checking it was the same issue.
You can never be too safe.
It's not immediately obvious that the latest release fixes this issue. Can you clarify as a matter of urgency please @Todd?
The latest security release addresses this issue, yes. We've been in contact with the firm that released this and they coordinated with us to get the security release out before they announced it.
Very standup of them I might add.
Thank you sir. Can you tell us which change was directed at this issue? I just want to be sure that no plugins expose the same vulnerability.
http://vanillaforums.org/discussion/comment/180288/#Comment_180288
Ah, sorry for the double post. There were some brief issues with the forum last night and I thought that comment had been lost.