Cross-site scripting via Asset-name JavaScript injection
Published May 28, 2025 · Updated May 28, 2025
Cross-site scripting in Best Practical RT 5.0.0 through 5.0.7 allows remote attackers to inject JavaScript through an Asset name. Public records identify the Asset-name rendering path but do not disclose the template or escaping operation that accepts the script-bearing value. Required asset permissions and browser interaction are undocumented, and the vendor release notes transpose the identifiers for this flaw and a permalink flaw.
Summary
What happened
Cross-site scripting in Best Practical RT 5.0.0 through 5.0.7 allows remote attackers to inject JavaScript through an Asset name. Public records identify the Asset-name rendering path but do not disclose the template or escaping operation that accepts the script-bearing value. Required asset permissions and browser interaction are undocumented, and the vendor release notes transpose the identifiers for this flaw and a permalink flaw.
The record
- CVE
- CVE-2025-31500
- Published
- May 28, 2025
- Updated
- May 28, 2025
- Vendor
- Best Practical Solutions LLC
- Product
- RT
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 2025CVE publishedPublication date reported by the CVE source.
- May 28, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.0.0 <5.0.8
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo