Stored XSS via unsanitized property name
Published Jan 2, 2020 · Updated Aug 6, 2024
Stored cross-site scripting in Jomres before 7.3.1 allows remote authenticated users to inject script through property_name. The property-detail editor stores the property_name POST value without proper sanitization, causing embedded HTML or script to execute when the malicious data is viewed. Business Manager permission is required, and the payload runs in another user's browser within the affected site's security context.
Summary
What happened
Stored cross-site scripting in Jomres before 7.3.1 allows remote authenticated users to inject script through property_name. The property-detail editor stores the property_name POST value without proper sanitization, causing embedded HTML or script to execute when the malicious data is viewed. Business Manager permission is required, and the payload runs in another user's browser within the affected site's security context.
The record
- CVE
- CVE-2013-3931
- Published
- Jan 2, 2020
- Updated
- Aug 6, 2024
- Vendor
- Jomres
- Product
- Jomres
- Classifications
- CWE-79
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 2, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 2024Record 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=before 7.3.1
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