







I've developed a new XSS scanner tool that's written in Javascript called XSS Rays for Microsoft. They have given me permission to release the tool as open source which is awesome because it can be used for other open source applications. I recommend you use it as part of the web development process to make sure you've filtered XSS correctly on your application. It works as a bookmarklet and scans any links, paths or forms on the target scanning page (even cross domain). You can add vectors to it quite easily and it includes some of the most common injections I've found on sites over the years. I've tested it on IE7/IE8 and Firefox but it could work in other browsers. The advantage of the bookmarklet is that vectors can be customised for each browser and they are executed in the context of the browser, in IE8 standards mode were css expressions are disabled in IE8 the vector won't be executed for example. Hopefully there should be no false positives either because each vector is actually executed and it reported back as successful, in fact if there is a false positive it will be a bug in my code (lets hope not). Technical details The code works by creating connections to the target links/paths using iframes, each iframe is assign a name which is the url to return to on successful execution (the originating url). This allows cross domain links to be checked. The vectors are stored in a simple object, each vector has the following properties:- input, name, browser, form, url, path (there's a optional second input). Input is the XSS vector, the string "XSS" is used to replace with a logger or a poc url and is required by all vectors. Name is just a meaningful name applied to the vector, browser supports ALL|FF|IE and helps to save time when testing specific browser vectors as XSS Rays will only target those versions for the vector. Form, url, path allows you to disable the vector for scanning forms etc, supports TRUE|FALSE. There are a few configuration properties supported:- 1. externalLog - Sends all executions to a external logger by default "http://127.0.0.1/XSSRays/logging/xsslogger.php", the vector is encoded and sent to a get variable xss and can be easily customised to log in another language, each field is sent tab separated. 2. excludeURLS - allows you to exclude certain urls from the scan, the variable is a regular expression so remember to double escape special characters. 3. sameorigin - When enabled it should stay to the same site and not scan external links, this has not be tested fully yet. There's a interesting little hack for IE to enable the onload event of a dynamic iframe, I use the following code to create a specific IE loader:- <pre lang="javascript"> var ieLoader = "document.getElementById('"+'ray'+self.uniqueID+"').ieonload()"; if(self.isIE()) { try { var iframe = document.createElement('<iframe name="'+location + '#xss'+'" onload="'+ieLoader+'">'); } catch (e) { var iframe = document.createElement('iframe'); } } else { var iframe = document.createElement('iframe'); } </pre> Download & Instructions Download here 1. You need to install a local web server like xampp:- http://www.apachefriends.org/en/xampp.html 2. Once installed copy the XSSRays directory to your web server root xampp root is :- C:\xampp\htdocs\ 3. Open the bookmarklet.html file in the helpers directory of XSSRays. Drag to your bookmarks toolbar on Firefox or on IE right click the link and click add to favorites (You might get a security warning in IE). 4. Find your web site that you wish to scan, click your bookmarklet. Then press CTRL+SHIFT+X which will now run XSS Rays on the target site. Thanks Big thanks to David Ross, Manuel Caballero and you (you know who you are) for testing and feedback. Thanks to Microsoft for supporting the development of XSS Rays. Updates.... The latest version of XSS Rays is now online (0.5.0), it contains some speed improvements and bug fixes. 1. Fixed conflicts with form elements with the name action or submit was causing form posts not to be submitted. Thanks Mike W 2. Removed unneeded cleanup code now the IE onload works. 3. Added the ability to exclude certain field types and names from being XSS'd. 4. Fixed name vector to specify window.name which was causing conflicts with image elements. 5. Fixed and checked same origin code. Thanks to Arshan who gave me a kick up the backside :) 6. Removed keyboard shortcut and added a button instead. New update 0.5.5 1. Fixed Firefox bug with same origin 2. Fixed form Post to allow field names with submit. Thanks Kuza55 for the awesome form post hack :)
Reducing XSS by way of Automatic Context-Aware Escaping in Template Systems
Posted by Jad S. Boutros, Security Team Building on our earlier posts on defenses against web application flaws [ "Automating Web Applicatio...

Universal XSS from website-driven element picker
### Summary As reported: > For the Firefox MV2 extension, it’s possible for a webpage to iframe the element picker and control it to add arbitrary trusted filters when a user clicks on the...
w3c/trusted-types
A browser API to prevent DOM-Based Cross Site Scripting in modern web applications.
chardetng: A More Compact Character Encoding Detector for the Legacy Web
chardetng is a new small-binary-footprint character encoding detector for Firefox written in Rust. Its purpose is user retention by addressing an ancient—and for non-Latin scripts page-destroying—Web compat problem that Chrome already addressed. It puts an end to the situation that some pages showed up as unreadable garbage in Firefox but opening the page in Chrome remedied the situation more easily than fiddling with Firefox menus. The deployment of chardetng in Firefox 73 marks the first time in the history of Firefox (and in the entire Netscape lineage of browsers since the time support for non-ISO-8859-1 text was introduced) that the mapping of HTML bytes to the DOM is not a function of the browser user interface language. This is accomplished at a notably lower binary size increase than what would have resulted from adopting Chrome’s detector. Also, the result is more explainable and modifiable as well as more suitable for standardization, should there be interest, than Chrome’s detector
shikoshib/winerr
A fast and accurate Windows fake error messages generator made with HTML5 Canvas
Running Interactive Scripts | Web Browser Engineering
The first web applications were like the previous chapter’s guest book, with the server generating new web pages for every user action. But in the early 2000s, JavaScript-enhanced web applications, which can update pages dynamically and respond immediately to user actions, took their place. Let’s add support for this key web technology to our browser.
XR Web Browsers - HackMD
Comparing the many web browsers offering a sliding scale of support and features with the latest VR/AR devices.
Supporting Embedded Content | Web Browser Engineering
While our browser can render complex styles, visual effects, and animations, all of those apply basically just to text. Yet web pages contain a variety of non-text embedded content, from images to other web pages. Support for embedded content has powerful implications for browser architecture, performance, security, and open information access, and has played a key role throughout the web’s history.
Improving the trustworthiness of Javascript on the Web
Today, there's no way to audit a site’s client-side code as it changes, making it hard to trust sites that use cryptography. We preview a specification we coauthored that adds auditability to the web.

UseMods
Zero-dependency JavaScript utilities for frontend and SSR — formatters, validators, generators, modifiers, and browser helpers.

Embedding The Web
We need to talk more The web is much more than browsers. What works great in browser development is missing in related spaces like embedding. Can we get together to collectively describe security and compatibility properties of user agents that are not browsers? Can we develop things that don’t ...
Behind the Scenes Hardening Firefox with Claude Mythos Preview – Mozilla Hacks - the Web developer blog
New details about what we found, and how agentic harnesses are now able to reproduce real bugs and dismiss false positives.

HTML papers on arXiv -- why it is important, and how we made it happen
In October 2023, arXiv made HTML formatted papers available to readers. This was the exciting outcome of over a year of accessibility research and development with the scientific community. Currently, only 2.4% of research outputs meet accessibility guidelines. Informed by scientists who rely on assistive technology, our analysis demonstrates that offering HTML is the most impactful step arXiv can take. Scientists need HTML now, and emphasize to not let perfect be the enemy of good enough. In this paper we share with you how arXiv is achieving HTML conversions from LaTeX now, and our plans for future improvements.

Make the Web Work For Everyone – Mozilla Hacks - the Web developer blog
Updated 2016/07/22: Commenters found a few data errors (thanks!) which have now been corrected. Millions of websites have compatibility problems on one or more of the major browsers, leading to ...

#atprotodev my prototype extension has been approved! Your thoughts? Tag your HTML with RDFa compliant at:// attrs and it gives you a context menu & at-ray vision 😊 Firefox: addons.mozilla.org/en-GB/firefox/addon/where-it-… Chrome: chromewebstore.google.com/detail/where-its-at/oemnpmaoj… Safari: github.com/jphastings/where-its-AT/relea…
Where it's AT – Get this Extension for 🦊 Firefox (en-GB)
addons.mozilla.org