stefanoquarta
Forum Replies Created
-
Hi,
just a quick update following our previous report.
Today we worked extensively with Woody Snippets for several hours, creating, editing, saving and reopening multiple PHP snippets, including fairly structured ones.
The issue we reported yesterday did not occur at all today. All snippets were saved and reopened normally, and the editor remained stable throughout the entire session.
We have not made any specific change on our side intended to solve the issue, so we cannot explain why the problem occurred yesterday and has not appeared again today.
We thought this additional information could be useful for your investigation.
We will let you know if the issue occurs again.
Hi,
thank you for your reply.
We can provide some additional information based on what we observed.
The issue does not seem to affect all newly created PHP snippets. We have created simple PHP snippets after the update and they can be saved and reopened normally.
We encountered the problem while creating some new, more structured PHP snippets that also included JavaScript and<script>blocks.
In those cases, the snippet could initially be created and saved. However, when reopening it, the code appeared correctly in the editor for a moment and then disappeared, leaving the editor empty.
Existing snippets created before the latest update, including complex snippets of this type, continue to work normally.
We also tested a very simple new PHP snippet containing a basic<script>block and that worked correctly, so the presence of JavaScript alone does not seem to be enough to trigger the issue.
The behaviour therefore appears to occur only under certain conditions with newly created snippets, which we have not yet been able to isolate.
Since we had been using this type of PHP/JavaScript snippet successfully before the latest update, we wanted to report the behaviour in case there has been a change in the editor, validation or sanitization process that could explain it.
Thank you for investigating.Hello,
I have received the same security alert from BlogVault regarding CVE-2026-66640 on a website where I currently use Login With AJAX.
BlogVault has also confirmed that no patched version is currently available and has recommended either contacting the plugin developers or replacing the plugin.
Could you please let us know whether you are working on a security update and whether a patched version will be released soon?
I would prefer to continue using Login With AJAX rather than replace it, so an update from the development team would be greatly appreciated.
Thank you.