OK so I have this issue with 3 separate sites. Logging turned on for 2 of them. Should I email the log? If it helps, on the Connected screen, it says connected but the Email address and Account name are blank. Logs also appear to be empty after clicking Sync.
We are checking on things on our own at the same time as we wait for potential feedback from you, so we’re definitely keeping an eye on things here.
If anyone needs to, we have provided a 1.14.1 release which still relies on the older API version 2 but has had the patchstack security fix applied to it
You can download it at https://downloads.wordpress.org/plugin/constant-contact-forms.1.14.1.zip
I can confirm that 1.14.1 does connect to existing lists. New installs of 2.0.1 do not. Interestingly, the site that I installed 2.0 first then 2.0.1 connects to lists just fine.
We have pushed out an update at version 2.0.2 which should help take care of some details about the overall process. We also adjust some rate limit issues for the API that the plugin uses, and that should also be helping to resolve experienced issues.
By all means please test on a staging site first, if you have one, to help confirm things are working better now. Thanks
Do you know if there’s any way with that website to get the reported locations for the issues? On the surface they’re very vague with actual details that would be useful for getting to the root.
I don’t – all I know is that we get reported these issues by iThemes Security which is powered by Patchstack. Here’s the iThemes report:
https://tinyurl.com/57ud2x9n
Thanks. That will hopefully help track some more and new details down.
This is definitely still in our radar and we are waiting for some other things to be confirmed before we do a new release that will further enhance these security issues.
Just thought I’d let you know I’m still getting security issue notifications for 2.0.3:
WordPress Constant Contact Forms plugin <= 2.0.3 – Broken Access Control vulnerability
Noted, but one question I have is if there’s any actual information being provided, or places that we could reach out to to get a more detailed report of where found issues are at? Right now it’s largely a case of “This plugin still has security issues” but doesn’t provide anything for where in the code base it’s at, and it’s not a small codebase at this point.
If Patchstack had a place to reach out to as the official authors of our plugin, to get privately disclosed more information that would be immensely helpful
@constantcontact, Patchstack says the issue was reported by Lana Codes with “no reply from the vendor.” So apparently they were unable to contact you. I suggest you reach out to them directly:
@solventweb I don’t personally have access to some of the accounts where someone may or may not have reached out to, so I can’t confirm or deny that. I do know that once myself and others directly involved with the development of the plugin were made aware, we definitely responded as quick as we could.
A left vs right hand communication issue potentially.
@caordawebsol Noted, and we’re still looking into getting more details.
Thank you.
