GoliveApplication · Apwide
CVE-2025-45939
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 · uneditedApwide Golive 10.2.0 Jira plugin allows Server-Side Request Forgery (SSRF) via the test webhook function.
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 Apwide Golive Jira plugin version 10.2.0 contains a Server-Side Request Forgery (SSRF) vulnerability in its test webhook function. An attacker can exploit this by supplying malicious URLs to the webhook test endpoint, potentially allowing the server to make unintended requests to internal infrastructure or external services.
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
GoliveApplication
= 10.2.0CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Apwide Golive plugin is installedNavigate to Jira administration > Apps > Manage apps, or check the filesystem at <Jira-install>/atlassian-jira/WEB-INF/plugins for Apwide Golive filesAffected if Apwide Golive plugin is not present in the Jira instance
-
Confirm the exact version of Apwide GoliveIn Jira admin > Apps > Manage apps, locate Apwide Golive and read the version column, or inspect the plugin descriptor file (atlassian-plugin.xml) for the plugin versionAffected if Version displayed is 10.2.0 exactly
-
Identify if webhook functionality is enabledNavigate to Apwide Golive app settings or project configuration where webhook features are managed, check if any webhook-related modules are activeAffected if Webhook configuration or test feature is accessible to users
-
Verify webhooks module is loadedCheck Jira's plugin-in-state or inspect the installed-apps REST API endpoint /rest/plugins/1.0/ to confirm the webhooks module is present and enabledAffected if Webhook test module is listed as enabled in Jira's plugin state
A Jira instance is affected if Apwide Golive version 10.2.0 is installed and the webhook test functionality is accessible and enabled.
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.
From vendor dataRestrict the webhook test function to only allow verified, internal, or explicitly permitted URLs through strict allowlist validation. Implement proper URL validation to prevent requests to internal network addresses and private IP ranges.
Fix this in Golive
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-45939 — 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-45939 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