CVE-2025-10787
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 vulnerability was found in MuYuCMS up to 2.7. Impacted is an unknown function of the file /index/index.html of the component Add Fiend Link Handler. Performing manipulation of the argument Link URL results in server-side request forgery. The attack may be initiated remotely. The exploit has been made public and could 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 confidenceMuYuCMS versions up to 2.7 contain a server-side request forgery (SSRF) vulnerability in the Add Friend Link Handler component at /index/index.html. The Link URL parameter is not properly validated, allowing remote attackers to trick the server into making arbitrary requests to internal or external resources.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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.
-
Confirm MuYuCMS installation and versionLocate the MuYuCMS installation directory and check for a version file, admin panel, or footer/header that displays the CMS version number. Common locations include a version.php file, config file, or the admin dashboard.Affected if The installed version is 2.7 or lower (including any version below 2.7).
-
Verify Add Friend Link Handler endpoint existsCheck if the file /index/index.html exists in the MuYuCMS web root and contains the Add Friend Link functionality. Access the URL path /index/index.html in a browser or via curl to confirm the endpoint is present and responds.Affected if The /index/index.html endpoint exists and loads the Add Friend Link component.
-
Identify Link URL parameter in the Add Friend Link formInspect the HTML source of the Add Friend Link page or intercept HTTP requests when the form is submitted. Look for an input parameter named 'Link', 'link', 'url', or similar that accepts a URL value.Affected if The form contains a Link URL parameter that accepts user-supplied input without visible server-side validation.
-
Check if the Link URL parameter lacks input validationSubmit a test request to the Add Friend Link endpoint with an internal URL (such as http://127.0.0.1 or http://localhost) as the Link URL value. Observe if the server accepts and attempts to process the request.Affected if The server accepts and attempts to fetch arbitrary URLs provided in the Link URL parameter without rejecting internal/private IP addresses or unvalidated destinations.
A user is affected if MuYuCMS version 2.7 or lower is installed and the Add Friend Link Handler at /index/index.html is accessible with an unvalidated Link URL parameter.
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 URL validation with a whitelist approach, disallow requests to internal/private IP ranges and localhost, and add proper input sanitization to the Link URL parameter.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10787 — 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-10787 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