CVE-2025-10410
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 · uneditedA security vulnerability has been detected in SourceCodester Link Status Checker 1.0. This vulnerability affects unknown code of the file index.php. The manipulation of the argument proxy leads to server-side request forgery. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used.
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 confidenceServer-side request forgery (SSRF) in SourceCodester Link Status Checker 1.0 allows remote attackers to make the server perform arbitrary HTTP requests via the unsanitized 'proxy' parameter in index.php, potentially accessing internal services or bypassing network restrictions.
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= 1.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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify Link Status Checker installationLocate the application directory (commonly in web root like /var/www/html/ or similar). Check for index.php and look for version indicators in source files, README, or meta tags.Affected if The installed version is Link Status Checker version 1.0 (or if version cannot be determined but the application is present)
-
Locate the vulnerable index.php fileFind index.php in the application root. Verify it contains code handling a 'proxy' parameter (search for $_GET['proxy'] or $_POST['proxy']).Affected if index.php exists and contains parameter handling for 'proxy' without proper validation
-
Verify the application is network-accessibleCheck if the web server hosting Link Status Checker is exposed to network requests (check firewall rules, web server configuration, and listening interfaces).Affected if The application is reachable from network (not localhost-only or firewalled off)
-
Inspect proxy parameter handling in source codeOpen index.php and examine the code flow where the 'proxy' parameter is used. Look for cURL requests or similar HTTP client calls that use the parameter value directly.Affected if The proxy parameter is used in HTTP requests without whitelist validation or sanitization
-
Check for outbound network restrictionsReview firewall rules or network segmentation policies controlling outbound connections from the web server. Verify if the server can initiate arbitrary outbound HTTP connections.Affected if The server has unrestricted outbound network access (no egress filtering)
You are affected if Link Status Checker version 1.0 is installed, the application is network-accessible, and the proxy parameter in index.php processes user input without validation.
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 dataImplement strict input validation with whitelist-based filtering on the proxy parameter to restrict allowed destinations, and apply network segmentation to limit server outbound connectivity to necessary endpoints only.
- Consultation4.0 h
- Implementation4.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10410 — 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-10410 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