Security readout for executives and security teams
Plain-English summary
This CVE describes an SSRF issue in Apwide Golive 10.2.0 for Jira. An attacker could misuse the test webhook function to make the Jira server send requests to unintended destinations. Business risk is moderate because impact is limited in the CVSS record, but Jira often has network access to internal systems.
Executive priority
Prioritize remediation during the next security maintenance window, faster if Jira can reach sensitive internal services. Lack of KEV or cited exploitation lowers urgency, but SSRF from Jira can create meaningful internal exposure.
Technical view
CVE-2025-45939 is CWE-918 SSRF in the Apwide Golive 10.2.0 Jira plugin test webhook function. The CVSS 3.1 score is 6.5 with network attack vector, high complexity, no privileges, no user interaction, changed scope, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely where Jira Server or Data Center runs Apwide Golive 10.2.0. The bundle does not provide CPEs, affected ranges beyond 10.2.0, or deployment-specific prerequisites.
Exploitation context
The source bundle does not cite active exploitation, public exploit use, or KEV listing. The CVSS vector indicates remote unauthenticated reachability, but high attack complexity. Treat this as a validation and patch-management priority, not confirmed emergency exploitation.
Researcher notes
Evidence is limited to the CVE description, CVSS vector, CWE-918 classification, and one Apwide reference. The bundle does not document a patch, proof of concept, vulnerable endpoint details, or affected ranges beyond Golive 10.2.0.
Mitigation direction
- Inventory Jira instances for Apwide Golive and identify any 10.2.0 deployments.
- Check Apwide guidance for fixed versions or recommended configuration changes.
- Upgrade or patch according to vendor instructions when a fixed release is identified.
- Restrict reachability to Jira and plugin functions where business workflows allow.
- Use outbound allow-listing or proxy controls for Jira server egress.
Validation and detection
- Confirm installed Apwide Golive plugin versions on all Jira Server/Data Center systems.
- Review Apwide release notes and CVE records for current affected-version details.
- Check Jira logs for unusual outbound webhook test activity.
- Review network telemetry for unexpected outbound requests from Jira hosts.
- Verify egress controls limit access to internal metadata and sensitive services.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-45939 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L2.23.7CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://golive.apwide.com/doc/latest/server-data-center/2025-06-06CVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.