dbcve.org
PlaneApplication

CVE-2026-30242

HIGH · 8.5 CVSS v3.1 Published 2026-03-06
Fix available
A fix is available. Upgrade to 1.2.3 or later.
See remediation →
91/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
Plane is an an open-source project management tool. Prior to version 1.2.3, the webhook URL validation in plane/app/serializers/webhook.py only checks ip.is_loopback, allowing attackers with workspace ADMIN role to create webhooks pointing to private/internal network addresses (10.x.x.x, 172.16.x.x, 192.168.x.x, 169.254.169.254, etc.). When webhook events fire, the server makes requests to these internal addresses and stores the response — enabling SSRF with full response read-back. This issue has been patched in version 1.2.3.

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

Plane's webhook URL validation in app/serializers/webhook.py only checks ip.is_loopback, failing to block private/internal network ranges (10.x.x.x, 172.16.x.x-172.31.x.x, 192.168.x.x) and cloud metadata endpoints (169.254.169.254). Attackers with workspace ADMIN role can create webhooks to internal addresses, triggering the server to make requests and return full responses—enabling SSRF.

MitigationUpgrade Plane to version 1.2.3 or later, which implements proper validation of private/internal network IP ranges in webhook URL validation.

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
PlaneApplication
Affected:< 1.2.3

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
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/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 your Plane version
    Check the Plane application version in the UI (typically in Settings > About) or via command line if you have direct access to the installation
    Affected if Version is below 1.2.3, meaning the vulnerability exists in your version
  2. Verify your role in any workspace
    Navigate to each workspace Settings > Members and check if your account has the ADMIN role in any workspace
    Affected if You have ADMIN role in at least one workspace, making you a potential attacker vector for this vulnerability
  3. Check for existing webhooks targeting private IPs
    In each workspace, go to Settings > Webhooks and review all webhook URLs. Inspect if any target IP addresses in ranges: 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, or 169.254.169.254
    Affected if Any webhook exists with a URL pointing to private/internal network addresses or cloud metadata endpoints
  4. Test webhook creation with internal IP
    As an ADMIN, attempt to create a new webhook with a URL pointing to 127.0.0.1, 10.0.0.1, 172.16.0.1, 192.168.1.1, or 169.254.169.254 to verify if the validation blocks or allows it
    Affected if The system allows webhook creation to private/internal IPs, confirming the validation is insufficient
  5. Review webhook request logs
    Check Plane server logs or network logs for any outbound requests from the Plane server to internal IP addresses that originated from webhook triggers
    Affected if The Plane server has made or attempted to make requests to internal/private network addresses

Your environment is affected if you run Plane version below 1.2.3 AND have users with workspace ADMIN role who can create webhooks that target private network ranges or cloud metadata endpoints.

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

Upgrade Plane to version 1.2.3 or later, which implements proper validation of private/internal network IP ranges in webhook URL validation.

Recommended fix High confidence

1.2.3

  1. Upgrade Plane to version 1.2.3 or later to remediate the SSRF vulnerability
  2. After upgrading, verify that webhook URL validation now properly blocks private/internal network addresses (10.x.x.x, 172.16.x.x, 192.168.x.x, 169.254.169.254, etc.)

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

Fix this in Plane Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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