CVE-2025-54964
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 inject arbitrary executables. If the Job Service is configured for local-only access, this may allow for privilege escalation in certain situations. If the Job Service is network accessible, this may allow remote command execution.
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 confidenceThe GXP Job Service in BAE SOCET GXP versions prior to 4.6.0.2 lacks proper input validation, allowing an attacker who can interact with the service to inject and execute arbitrary executables. When the Job Service is network-accessible, this enables remote command execution; when local-only, it can be leveraged for privilege escalation.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Verify BAE SOCET GXP installationLocate the SOCET GXP installation on the system using standard software inventory or file system inspection methodsAffected if The software is present on the system
-
Determine installed versionCheck the version information for the installed SOCET GXP instance (typically accessible via program properties, version file, or the executable)Affected if The installed version is prior to 4.6.0.2
-
Inspect Job Service accessibilityExamine the Job Service configuration to determine whether it is bound to network-accessible interfaces or configured for local-only accessAffected if The Job Service is network-accessible (allowing remote command execution) or accessible to users with local access (allowing privilege escalation)
The environment is affected if BAE SOCET GXP is installed with a version prior to 4.6.0.2 and the Job Service is accessible, regardless of whether it is network-facing or local-only.
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 to obtain the patch. Additionally, restrict the Job Service to local-only access if network accessibility is not required, as this limits the attack surface.
SOCET GXP 4.6.0.2
- Verify current SOCET GXP version through the administration interface or system information
- Create a complete backup of the SOCET GXP configuration, databases, and associated data
- Review the official BAE Systems SOCET GXP 4.6.0.2 release notes for any specific upgrade requirements or注意事项
- Download the SOCET GXP 4.6.0.2 upgrade package from the official BAE Systems or Geospatial Exploitation Products download portal
- Execute the upgrade following the official installation/upgrade guide provided by BAE Systems
- Verify the upgrade was successful by checking the software version displays 4.6.0.2 or later
- Test the GXP Job Service functionality to confirm normal operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54964 — 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-54964 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