Browser script execution via contact form markup
Published Mar 4, 2024 · Updated Aug 28, 2024
Cross-site scripting in the Flusity CMS 2.33 contact form allows remote attackers to execute script in a user's browser. The form accepts an img element carrying an onerror handler and renders it as active markup instead of neutralizing it. A user must view the affected output, after which the injected script runs in that site's browser context.
Summary
What happened
Cross-site scripting in the Flusity CMS 2.33 contact form allows remote attackers to execute script in a user's browser. The form accepts an img element carrying an onerror handler and renders it as active markup instead of neutralizing it. A user must view the affected output, after which the injected script runs in that site's browser context.
The record
- CVE
- CVE-2024-27680
- Published
- Mar 4, 2024
- Updated
- Aug 28, 2024
- Vendor
- Flusity
- Product
- Flusity CMS
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 4, 2024CVE publishedPublication date reported by the CVE source.
- Aug 28, 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=2.3.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Flusity CMS contact-form XSS proof of conceptproof of concept · demonstrated
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