CVE-2025-54963
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 · uneditedAn issue was discovered in BAE SOCET GXP before 4.6.0.2. An attacker with the ability to interact with the GXP Job Service may submit a crafted job request that grants read access to files on the filesystem with the permissions of the GXP Job Service process. The path to a file is not sanitized for directory traversal, potentially allowing an attacker to read sensitive files in some configurations.
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 · high confidenceBAE SOCET GXP before version 4.6.0.2 contains a path traversal vulnerability in the GXP Job Service. An attacker who can submit job requests to the service can manipulate file paths to read files outside the intended directory, with the same permissions as the GXP Job Service process runs under.
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.6.0.2CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Identify installed BAE SOCET GXP versionLocate the GXP installation directory and check the version information. Common locations include the program files folder or check the application metadata. Look for version.txt, about dialog, or check the executable properties of socetgxp.exe or related binaries.Affected if The installed version is any version before 4.6.0.2 (e.g., 4.5.x, 4.4.x, etc.)
-
Confirm GXP Job Service is installed and runningCheck Windows Services for 'GXP Job Service' or 'Socet GXP Job Service', or use command 'sc query' to enumerate running services. Also check for related processes in Task Manager.Affected if The GXP Job Service is installed and running as a Windows service on the system
-
Determine network accessibility of GXP Job ServiceReview firewall rules and service binding configuration to determine if the GXP Job Service port is accessible from network hosts. Check if the service listens on localhost only or on all interfaces.Affected if The GXP Job Service port is exposed to untrusted network segments or the service accepts requests from non-localhost sources
A system is affected if BAE SOCET GXP version is before 4.6.0.2 AND the GXP Job Service is running and accessible to the attacker.
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.6.0.2
Upgrade to BAE SOCET GXP version 4.6.0.2 or later. If immediate patching is not possible, restrict access to the GXP Job Service to trusted users only and monitor for suspicious job request patterns.
4.6.0.2
- Identify the current SOCET GXP version currently installed
- Schedule a maintenance window for the upgrade
- Obtain SOCET GXP version 4.6.0.2 from official BAE Systems or Geospatial Exploitation Products distribution channels
- Follow BAE Systems upgrade documentation to apply the update
- After upgrading, verify the GXP Job Service is running the patched version
- Test that the path traversal vulnerability is mitigated by ensuring job requests cannot access files outside intended directories
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54963 — 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-2025-54963 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