dbcve.org
Socet GxpApplication · Baesystems

CVE-2025-54968

HIGH · 8.8 CVSS v3.1 Published 2025-10-27
Fix available
A fix is available. Upgrade to 4.6.0.2 or later.
See remediation →
94/100
Remediation priority · Urgent
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 Service does not require authentication. In some configurations, this may allow remote users to submit jobs, or local users to submit jobs that will execute with the permissions of other users.

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 confidence

The SOCET GXP Job Service in versions before 4.6.0.2 lacks authentication requirements, enabling unauthenticated remote attackers to submit jobs or local users to submit jobs that execute with the permissions of other users. This is an authentication bypass vulnerability that could lead to unauthorized command execution and privilege escalation.

MitigationUpgrade to BAE SOCET GXP version 4.6.0.2 or later which includes authentication requirements for the Job Service. As a compensating control, restrict network access to the Job Service to trusted IPs only.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Identify installed SOCET GXP version
    Locate the SOCET GXP installation directory and check the version information, typically found in the software's About dialog, version file, or installation logs. Common locations include the program's main executable properties or registry entries under the BAE Systems software installation path.
    Affected if The installed version is any version prior to 4.6.0.2, or if the version cannot be determined and the software is present.
  2. Verify if Job Service is running
    Check if the SOCET GXP Job Service is currently running on the system. This can be done through Windows Services (services.msc) looking for a service related to SOCET GXP Job Service, or via command line using 'sc query' or 'tasklist' to find the job service process.
    Affected if The Job Service is running and the software version is below 4.6.0.2.
  3. Determine Job Service network exposure
    Check if the Job Service is listening on network ports by reviewing firewall rules, netstat output, or the service configuration. The Job Service typically communicates over specific ports that should be restricted to trusted networks.
    Affected if The Job Service is listening on network-accessible ports (especially if accessible from untrusted networks) and the version is below 4.6.0.2.
  4. Review Job Service authentication configuration
    Examine the Job Service configuration files or settings to determine whether authentication is enforced. Look for configuration parameters related to authentication, security, or access control within the SOCET GXP installation directory or configuration folders.
    Affected if Authentication is disabled or not configured for the Job Service, and the version is below 4.6.0.2.

The environment is affected if SOCET GXP version is identified as below 4.6.0.2 and the Job Service is running and accessible, as the lack of authentication allows unauthorized job submission.

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 to BAE SOCET GXP version 4.6.0.2 or later which includes authentication requirements for the Job Service. As a compensating control, restrict network access to the Job Service to trusted IPs only.

Recommended fix Moderate confidence

4.6.0.2

  1. Identify the current version of BAE SOCET GXP installed in the environment
  2. Consult BAE Systems official documentation or support channels for the upgrade procedure to version 4.6.0.2
  3. Back up all current SOCET GXP configurations and data according to organizational backup procedures
  4. Apply the upgrade to version 4.6.0.2 following BAE Systems' official upgrade documentation
  5. Verify the upgrade was successful by checking the SOCET GXP version
  6. Test that the Job Service now requires authentication and functions correctly

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
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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