dbcve.org
LinkaceApplication

CVE-2026-30953

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to after 2.0.0 or later.
See remediation →
71/100
Remediation priority · Elevated
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
LinkAce is a self-hosted archive to collect website links. When a user creates a link via POST /links, the server fetches HTML metadata from the provided URL (LinkRepository::create() calls HtmlMeta::getFromUrl()). The LinkStoreRequest validation rules do not include NoPrivateIpRule, allowing server-side requests to internal network addresses, Docker service hostnames, and cloud metadata endpoints. The project already has a NoPrivateIpRule class (app/Rules/NoPrivateIpRule.php) but it is only applied in FetchController.php (line 99), not in the primary link creation path.

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

LinkAce is vulnerable to Server-Side Request Forgery (SSRF) in the link creation endpoint. When a user creates a link via POST /links, the server fetches HTML metadata from the user-supplied URL. The LinkStoreRequest validation is missing the NoPrivateIpRule, allowing attackers to target internal network addresses, Docker service hostnames, and cloud metadata endpoints (e.g., AWS 169.254.169.254). The project already has a NoPrivateIpRule class but it is only applied in FetchController.php, not in the primary link creation path.

MitigationAdd the NoPrivateIpRule validation rule to the LinkStoreRequest class to prevent the server from fetching metadata from internal/private IP addresses during link creation.

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
LinkaceApplication
Affected:<= 2.0.0

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Confirm LinkAce installation and version
    Locate the LinkAce installation directory and check the version. Common locations: check composer.json, version file, or the admin dashboard for the installed version number.
    Affected if The installed version is 2.0.0 or lower.
  2. Locate LinkStoreRequest validation file
    Find the LinkStoreRequest.php file in the app/Http/Requests/ directory of the LinkAce installation.
    Affected if The file exists and contains link creation validation logic.
  3. Check for NoPrivateIpRule in LinkStoreRequest
    Open LinkStoreRequest.php and examine the rules() method. Look for the presence of NoPrivateIpRule in the validation rules array.
    Affected if NoPrivateIpRule is NOT present in the validation rules for the URL field.
  4. Verify the metadata fetching feature is active
    Check if the application performs URL metadata fetching during link creation. This is typically enabled by default. Look for code that fetches HTML from the submitted URL during POST /links processing.
    Affected if The metadata fetching feature is enabled and functional.
  5. Confirm the vulnerable endpoint is accessible
    Verify the POST /links endpoint exists and accepts user input. This is the standard link creation endpoint in LinkAce.
    Affected if The endpoint is accessible and processes user-supplied URLs.

A user is affected if they run LinkAce version 2.0.0 or lower AND the LinkStoreRequest validation lacks the NoPrivateIpRule for URL fields, allowing SSRF attacks against internal services.

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.

From vendor data
Upgrade available Upgrade to a release after 2.0.0
Interim mitigation

Add the NoPrivateIpRule validation rule to the LinkStoreRequest class to prevent the server from fetching metadata from internal/private IP addresses during link creation.

Fix this in Linkace Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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