asymmetric-effort SpecifyJS up to 0.2.135 cross site scripting

Summaryinfo

A vulnerability classified as problematic has been found in asymmetric-effort SpecifyJS up to 0.2.135. Affected by this issue is some unknown functionality. Performing a manipulation results in cross site scripting. This vulnerability is reported as CVE-2026-50290. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in asymmetric-effort SpecifyJS up to 0.2.135. It has been classified as problematic. This affects some unknown processing. The manipulation with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity. The summary by CVE is:

SpecifyJS is a declarative TypeScript user interface framework. Prior to version 0.2.136, CSS value sanitization stripped `expression(` and `url(javascript:` using simple regex, but could be bypassed with CSS unicode escapes (`\65xpression(`), null bytes, or CSS comments (`exp/**/ression(`). These CSS injection vectors only work in legacy browsers (IE6-IE10). SpecifyJS targets modern browsers. Starting in version 0.2.136, CSS sanitization now normalizes unicode escapes and strips CSS comments before pattern matching. Also checks for `behavior:`, `-moz-binding`, and `-o-link` patterns.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-50290 since 06/04/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.

Upgrading to version 0.2.136 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• asymmetric-effort

Name

• SpecifyJS

Version

• 0.2.135

Website

• Product: https://github.com/asymmetric-effort/specifyjs/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion