dbcve.org
Socet GxpApplication · Baesystems

CVE-2025-54970

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-27
Fix available
A fix is available. Upgrade to 4.6.0.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
An issue was discovered in BAE SOCET GXP before 4.6.0.2. The SOCET GXP Job Status Service fails to authenticate requests. In some configurations, this may allow remote or local users to abort jobs or read information without the permissions of the job owner.

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

The SOCET GXP Job Status Service in versions prior to 4.6.0.2 does not properly authenticate incoming requests. This allows unauthenticated remote or local users to abort running jobs and read job information without proper authorization checks, bypassing the intended permission model of job ownership.

MitigationUpgrade BAE SOCET GXP to version 4.6.0.2 or later to obtain the patched Job Status Service with proper authentication. Review configurations where unauthenticated access may have been possible.

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
Socet GxpApplication
Affected:< 4.6.0.2

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

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

  1. Identify installed SOCET GXP version
    Locate the SOCET GXP installation and determine the exact version number through the software's about dialog, installation directory version file, or system-installed programs list
    Affected if The installed version is any release prior to 4.6.0.2
  2. Verify Job Status Service is present and running
    Check for the SOCET GXP Job Status Service in the list of running Windows services or processes, typically visible as a service named related to Job Status or GXP status monitoring
    Affected if The Job Status Service is installed and running on the system
  3. Test unauthenticated access to Job Status Service
    Attempt to access the Job Status Service API or interface without providing any authentication credentials - for example, by making a local or remote request to the service endpoint if exposed over network
    Affected if The service accepts and processes requests without requiring authentication or authorization
  4. Inspect Job Status Service configuration
    Review configuration files or settings associated with the Job Status Service to determine whether authentication enforcement is enabled or configured
    Affected if Authentication is disabled, not enforced, or improperly configured in the service settings

A system is affected if it runs any version of Baesystems SOCET GXP prior to 4.6.0.2 with the Job Status Service accessible without authentication credentials.

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 4.6.0.2 or later
Fixed in 4.6.0.2
Interim mitigation

Upgrade BAE SOCET GXP to version 4.6.0.2 or later to obtain the patched Job Status Service with proper authentication. Review configurations where unauthenticated access may have been possible.

Recommended fix High confidence

4.6.0.2

  1. Verify the current installed version of SOCET GXP by checking the application or system information
  2. Back up all SOCET GXP databases, configuration files, and user data according to enterprise backup procedures
  3. Download SOCET GXP version 4.6.0.2 or later from the BAE Systems geospatial portal (geospatialexploitationproducts.com) or authorized distribution channel
  4. Stop all SOCET GXP services, including the Job Status Service, using the appropriate service management tool
  5. Run the installer for version 4.6.0.2 following the BAE Systems installation guide for your platform
  6. After installation, verify the new version number matches 4.6.0.2 or later
  7. Restart all SOCET GXP services
  8. Test the Job Status Service to confirm authentication is now required for job operations

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

Fix this in Socet Gxp Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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