dbcve.org
Fme ServerApplication · Safe

CVE-2022-38339

MEDIUM · 6.1 CVSS v3.1 Published 2022-09-19
Fix available
A fix is available. Upgrade to 2021.2.6 / 2022.0.1.1 or later.
See remediation →
68/100
Remediation priority · Elevated
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
Safe Software FME Server v2021.2.5, v2022.0.0.2 and below contains a cross-site scripting (XSS) vulnerability which allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the login page.

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

Safe Software FME Server contains a cross-site scripting (XSS) vulnerability in the login page that allows attackers to inject arbitrary web scripts or HTML through a crafted payload.

MitigationUpgrade to a patched version of FME Server or apply vendor-provided security update; implement proper input validation and output encoding on login page form fields.

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
Fme ServerApplication
Affected:< 2021.2.6>= 2022.0.0.0, < 2022.0.1.1

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
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 checks

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

  1. Identify if FME Server is installed
    Check for FME Server installation by looking for the product in your system. On Windows, look for Safe Software folder in Program Files or check for FME Server services. On Linux, check for FME Server processes or installation directories.
    Affected if FME Server is not found on the system, then this CVE does not apply.
  2. Determine installed FME Server version
    Access the FME Server web interface and look at the version information, typically found in the footer of pages or in the Admin > Server Statistics section. Alternatively, check installation logs or version files in the FME Server installation directory.
    Affected if The installed version cannot be determined or is not visible.
  3. Compare version against affected ranges
    Review the version identified in step 2. Affected versions are: any version less than 2021.2.6, OR any version from 2022.0.0.0 up to but not including 2022.0.1.1.
    Affected if The installed version falls within < 2021.2.6 OR >= 2022.0.0.0 AND < 2022.0.1.1.
  4. Verify login page is accessible
    Confirm the FME Server login page is accessible via web browser at the standard FME Server web interface URL (commonly port 8080 or 443). The vulnerability exists in the login page form fields.
    Affected if The login page is exposed and the version is in the affected range, then the system is vulnerable to XSS injection.

If FME Server is installed and its version is either below 2021.2.6 or between 2022.0.0.0 and 2022.0.1.0 (inclusive), and the login page is accessible, the environment is affected by this CVE.

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
Upgrade available Upgrade to 2021.2.6 / 2022.0.1.1 or later
Fixed in 2021.2.62022.0.1.1
Interim mitigation

Upgrade to a patched version of FME Server or apply vendor-provided security update; implement proper input validation and output encoding on login page form fields.

Recommended fix High confidence

FME Server 2021.2.6 or later for 2021.x branch; FME Server 2022.0.1.1 or later for 2022.x branch

  1. 1. Identify the currently installed FME Server version by checking the FME Server Web Interface or system information
  2. 2. For FME Server 2021.x versions: Plan an upgrade to version 2021.2.6 or later
  3. 3. For FME Server 2022.0.x versions: Plan an upgrade to version 2022.0.1.1 or later
  4. 4. Review Safe Software's upgrade documentation and release notes for upgrade procedures
  5. 5. Perform a backup of the FME Server configuration and databases before upgrading
  6. 6. Execute the upgrade following Safe Software's recommended upgrade path for your specific version
  7. 7. After upgrade, verify the login page is functioning correctly and the XSS vulnerability is resolved
  8. 8. Consider performing a security scan or penetration test to confirm the remediation
Caveat Review Safe Software release notes for any configuration changes or breaking changes between your current version and the target version before upgrading

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

Fix this in Fme Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38339 — 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-2022-38339 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