@paddocknews Last time there was Julien Ingrassia commenting and if I remember correctly, he described that new generation make notes digitally. So I think it is all like expected.
@manicode But seems, that you reach to that parameter yourself as well. The question originally was only about sending. For reading, if you don't have ACAO setup opportunity, then I there is always old-not-so-good JSONP.
@manicode So the boolean answer is yes, that's why we have CSRF attacks :) Just need to use XHR param ".withCredentials=true;" and rest of it must be CORS-safelisted (previously known as Simple Request) compatible
Also I have proposed related requirement on the topic to @OWASP_ASVS (not yet released v5.0, bleeding edge):
V3.4.6 Verify that cookie-based session tokens are only transferred in Set-Cookie and Cookie headers.
... but for Drupal the issue was a bit wider.
From July 2022, Drupal has released 9 Security Advisories for CORE, and I have caused 2 of them. Previously SA-CORE-2022-014, and now SA-CORE-2023-004:
https://t.co/8XLmmcV9oo
After years of hearing questions like "Do you have any course that teaches how to make stuff more secure instead of only breaking it?" we finally have a course about configuring services to reduce their attack surface! https://t.co/j6ObCW9FqM
@OctagonNetworks Everyone seems to use document.write for writing HTML here. But the problem exists even when we change document.write with console.log. Shortest known payload 21 symbols. Were you aware of this, @OctagonNetworks ?