dbcve.org
Socet GxpApplication · Baesystems

CVE-2025-54969

MEDIUM · 6.1 CVSS v3.1 Published 2025-10-27
Fix available
A fix is available. Upgrade to 4.6.0.2 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
An issue was discovered in BAE SOCET GXP before 4.6.0.2. The SOCET GXP Job Status Service does not implement CSRF protections. An attacker who social engineers a valid user into clicking a malicious link or visiting a malicious website may be able to submit requests to the Job Status Service without the user's knowledge.

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 BAE SOCET GXP Job Status Service lacks CSRF protection mechanisms, allowing attackers to forge authenticated requests. An attacker can trick a logged-in user into unknowingly submitting requests to the Job Status Service by leveraging social engineering techniques such as malicious links or websites.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) for all state-changing operations and configure SameSite cookies on session cookies to prevent cross-origin request forgery.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:L

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 SOCET GXP version
    Locate the installed BAE Systems SOCET GXP version through the application GUI, Help > About menu, or product documentation. If using a command-line interface, check the version using the product's built-in version command if available.
    Affected if The installed version is lower than 4.6.0.2 (e.g., 4.5.x, 4.4.x, or earlier releases).
  2. Confirm Job Status Service is accessible
    Verify the Job Status Service endpoint is exposed and reachable. This is typically a web service component that handles job submission and status queries. Check if the service is enabled in the application configuration or accessible via browser if it has a web interface.
    Affected if The Job Status Service is enabled and accessible to users.
  3. Inspect session cookie configuration
    Log into the SOCET GXP application and examine the session cookies using browser developer tools (Application/Storage tab) or by intercepting HTTP responses. Look for the SameSite attribute on session cookies.
    Affected if Session cookies do not have the SameSite attribute set, or it is set to None without Secure flag.
  4. Check for anti-CSRF token implementation
    Submit a state-changing request to the Job Status Service (such as a job submission) and inspect the HTTP request/response. Look for a CSRF token parameter or header in the request, or a token field in the application forms.
    Affected if No CSRF token, anti-CSRF token, or synchronizer token pattern is present in requests to the Job Status Service.

The environment is affected if SOCET GXP version is below 4.6.0.2 AND the Job Status Service is accessible AND no CSRF protection (tokens or SameSite cookies) is implemented.

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

Implement anti-CSRF tokens (synchronizer token pattern) for all state-changing operations and configure SameSite cookies on session cookies to prevent cross-origin request forgery.

Recommended fix High confidence

4.6.0.2

  1. Contact BAE Systems or your authorized SOCET GXP reseller to obtain the version 4.6.0.2 upgrade package
  2. Obtain and review the official SOCET GXP upgrade documentation from BAE Systems
  3. Schedule a maintenance window for the upgrade process
  4. Back up the current SOCET GXP installation and configuration data
  5. Apply the version 4.6.0.2 upgrade following BAE Systems' documented upgrade procedure
  6. Verify the upgrade was successful by checking the SOCET GXP version number
  7. Confirm the Job Status Service is functioning correctly after the upgrade

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

Fix this in Socet Gxp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
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,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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