dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-2513

HIGH · 8.6 CVSS v4.0 Published 2026-03-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
A vulnerability exists in Progress Flowmon ADS versions prior to 12.5.5 and 13.0.3, whereby an administrator who clicks a malicious link provided by an attacker may inadvertently trigger unintended actions within their authenticated web session.

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 confidence

This is a Cross-Site Request Forgery (CSRF) vulnerability in Progress Flowmon ADS. An authenticated administrator who clicks a malicious link crafted by an attacker will have their browser send unintended requests to the application using their valid session cookies, allowing the attacker to trigger administrative actions without authorization.

MitigationUpgrade Progress Flowmon ADS to version 12.5.5 or 13.0.3 or later to obtain the vendor patch that addresses this CSRF vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Flowmon ADS version
    Access the Flowmon web interface admin panel and navigate to System > About or check the version via CLI command 'flowmon --version' if available on the system
    Affected if The displayed version is below 12.5.5 or between 13.0.0 and 13.0.2 (inclusive)
  2. Confirm web interface is accessible
    Verify that the Flowmon ADS web management interface is reachable over HTTP/HTTPS on the configured port (typically 443 or 8443)
    Affected if The web interface is exposed and accessible from network locations where untrusted links could be clicked
  3. Check for active administrator sessions
    In the web interface, navigate to Administration > Sessions or similar session management area to view active authenticated administrator sessions
    Affected if Administrator sessions are active and could be leveraged for session-based attacks
  4. Review admin activity logs for suspicious requests
    Examine Flowmon ADS logs (typically in /var/log/flowmon/ or via the web interface logging section) for any unexpected or unauthorized admin actions
    Affected if Logs show admin actions initiated from unexpected IP addresses or URLs that the admin does not recognize
  5. Verify CSRF protection configuration
    Check the web application configuration files or settings for presence of CSRF token enforcement and SameSite cookie attributes
    Affected if CSRF protection is disabled or not properly configured in the web application settings

A user is affected if their Flowmon ADS version is below 12.5.5 or between 13.0.0 and 13.0.2, and the web management interface is accessible to administrators who could click malicious links.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Progress Flowmon ADS to version 12.5.5 or 13.0.3 or later to obtain the vendor patch that addresses this CSRF vulnerability.

Recommended fix Moderate confidence

Flowmon ADS 12.5.5 or 13.0.3 (or later)

  1. Obtain the appropriate upgrade package for your current Flowmon ADS version (12.x or 13.x) from Progress official channels
  2. Review the official Flowmon ADS upgrade documentation for your version
  3. Ensure you have a complete backup of the current Flowmon ADS configuration and database
  4. Schedule a maintenance window to minimize impact on production monitoring
  5. Download Flowmon ADS version 12.5.5 or 13.0.3 (or later) from the Progress customer portal
  6. Stop all Flowmon ADS services before beginning the upgrade
  7. Run the upgrade installer following the documented upgrade procedure
  8. After upgrade completion, verify all services start successfully
Caveat Review release notes for any configuration changes or deprecated features between your current version and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2513 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2513 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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