CVE-2026-2098
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAgentFlow developed by Flowring has a Reflected Cross-site Scripting vulnerability, allowing unauthenticated remote attackers to execute arbitrary JavaScript codes in user's browser through phishing attacks.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAgentFlow contains a reflected cross-site scripting (XSS) vulnerability where user-supplied input is improperly sanitized and reflected back in HTTP responses without encoding, allowing execution of arbitrary JavaScript in victim browsers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.0.0.1878.877CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Flowring Agentflow is installedIdentify whether Flowring Agentflow software is present on the system. Check for installation directories, services, or applications named 'Agentflow' or 'Flowring'. This may involve checking installed programs on Windows, or package listings on Linux systems.Affected if Flowring Agentflow is found on the system
-
Determine installed Agentflow versionLocate and read the version information for the installed Agentflow instance. Common locations include: About dialogs within the application, installation logs, version files in the installation directory, or the product's system information page. Compare the discovered version number against 4.0.0.1878.877.Affected if Installed version is lower than 4.0.0.1878.877
-
Verify web interface accessibilityDetermine if the Agentflow web interface is accessible over HTTP/HTTPS. Check if the application runs a web server component and identify its listen address and port. This may require reviewing service configurations or network binding settings.Affected if The Agentflow web interface is accessible to users or network segments where the vulnerability could be triggered
-
Identify user input reflection pointsIf the web interface is accessible, review application URLs and parameters that accept user input. Look for query parameters, form inputs, or path segments that might be reflected in server responses without encoding. Common areas include search functions, error messages, and navigation parameters.Affected if User-supplied input is reflected in HTTP responses without proper encoding
A system is affected if Flowring Agentflow version is below 4.0.0.1878.877 and has an accessible web interface that reflects user input in responses.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.0.0.1878.877
Implement context-sensitive output encoding and input validation for all user-controlled data fields, and apply Content Security Policy (CSP) headers to mitigate XSS execution.
AgentFlow version 4.0.0.1878.877 or later
- Contact Flowring (the vendor) to obtain the fixed version of AgentFlow (4.0.0.1878.877 or later)
- Ensure you have a complete backup of your current AgentFlow installation and database before proceeding
- Follow Flowring's official upgrade documentation to install version 4.0.0.1878.877 or the latest available version
- After upgrading, verify that the XSS vulnerability is no longer present by testing for reflected parameters in URLs
- Monitor for any post-upgrade issues and consult vendor release notes for any additional configuration requirements
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2098 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2098 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data