CVE-2025-71458: FTS3 Web Monitoring 3.12.0 through 3.13.2 and 3.14.0 SQL Injection via /linkinfo

Published Nov 6, 2026

Updated

FTS3 Web Monitoring (fts-monitoring) versions 3.12.0 through 3.13.2 and 3.14.0 contain an unauthenticated sql injection vulnerability in the /linkinfo endpoint handled by getlinkinfo. Remote attackers can inject SQL through the sourcese and destse query parameters to perform blind injection and read stored cloud storage credentials and token provider client secrets.

Event History

Nov 6, 2026

CVE Published

via MITRE·12:20 AM

Data Sourced

via MITRE·12:20 AM

DescriptionSeverityWeakness

Frequently Asked Questions

Which deployments are exposed?

FTS3 Web Monitoring (fts-monitoring) versions 3.12.0 through 3.13.2 and version 3.14.0 are affected. The vulnerable functionality is the /linkinfo endpoint.

Does an attacker need an account or user interaction to exploit this issue?

No. The issue is unauthenticated and remotely exploitable, with no user interaction required.

What can an attacker obtain through exploitation?

An attacker can use blind SQL injection through the source_se and dest_se query parameters to read stored cloud storage credentials and token provider client secrets.

How can I determine whether my instance is being targeted or affected?

Review requests to /linkinfo, particularly source_se and dest_se query parameter values, for unexpected or injection-like input. Confirm whether the deployed fts-monitoring version is within 3.12.0 through 3.13.2 or is 3.14.0.

CVE-2025-71458: FTS3 Web Monitoring 3.12.0 through 3.13.2 and 3.14.0 SQL Injection via /linkinfo

Event History

Frequently Asked Questions

Which deployments are exposed?

Does an attacker need an account or user interaction to exploit this issue?

What can an attacker obtain through exploitation?

How can I determine whether my instance is being targeted or affected?

Company

Resources

Contact

Frequently Asked Questions

Which deployments are exposed?

Does an attacker need an account or user interaction to exploit this issue?

What can an attacker obtain through exploitation?

How can I determine whether my instance is being targeted or affected?