Closed (cannot reproduce)
Project:
Webform
Version:
7.x-4.15
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
19 Sep 2017 at 19:12 UTC
Updated:
14 Jun 2019 at 13:39 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
bretbenziger commentedI'm also getting this security alert.
Comment #3
sainsley commentedI'll third that. I am getting it also.
Comment #4
jackalope commentedSame here on many Drupal 7 sites that we monitor and maintain.
Comment #5
jackalope commentedComment #6
upunkt commentedSame here. Since I do not find reasonable advice or hints about a vulnerability I keep the current version for the moment. Still, someone of the maintainers please clarify.
Comment #7
joelstein commentedDitto. I see the alert on a site with the 7.x-3.x branch installed.
Comment #8
dfriedman12 commentedI also see the same alert as #7 with Webform 7.x 3.27.
Comment #9
upperholme commentedDitto
Comment #10
agnesliu commentedIt's also on my website (webform 7.x-4.15). Any ideas?
Comment #11
tvaughn78 commentedHave this alert too. Came here to make sure 15 is after 12 :p
Comment #12
keithn commentedToday, one day after reporting the issue, I no longer get this error. I checked a bunch of my sites which use webform on different servers and simplytest.me.
I love it when something fixes itself :-)
Keith
Comment #13
criscomSame for me and still showing.
Comment #14
liam morlandMaintainer here. I'm not seeing this problem. 7.x-4.15 is after 7.x-4.12. It might help to clear cache and check for updates again.
Comment #15
upunkt commentedThanks Liam. One thing came into my mind. Could there be a vulnerability in 4.12 and some skilled person managed to try to trick site maintainers to downgrade? How could this be checked?
Comment #16
liam morlandIt is possible that the update process was getting out-of-date information. Let's say that drupal.org announced what the latest version is, and mistakenly says 7.x-4.12, sites might see that they have a different version and raise it as an issue. They may not do any version comparison. Someone who is seeing this problem would have to add debugging output to the update manager code to see what is going on.
Comment #17
liam morlandIf you are still seeing this, please re-open and provide details.