CVE-2025-14197
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 Verysync 微力同步 up to 2.21.3. The impacted element is an unknown function of the file /rest/f/api/resources/f96956469e7be39d of the component Web Administration Module. Such manipulation leads to information disclosure. The attack can be executed remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceAn information disclosure vulnerability exists in the Verysync 微力同步 Web Administration Module. The affected endpoint is /rest/f/api/resources/f96956469e7be39d, which exposes sensitive information without proper authorization. The vulnerability is remotely exploitable and a public exploit exists.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Verysync is installedLocate the Verysync executable or service on the system (common paths: C:\Program Files\Verysync or /usr/bin/verysync). Check running processes for verysync.exe or verysync binary.Affected if Verysync software is present on the system
-
Confirm web admin interface is enabledCheck Verysync configuration files (verysync.json or config.json in the data directory) for web admin settings. Look for 'webUI' or 'http' related configuration sections that enable the web server.Affected if Web administration interface is enabled in configuration
-
Test unauthenticated access to vulnerable endpointWith the web admin port open (default 8886), attempt to access http://<target>:8886/rest/f/api/resources/f96956469e7be39d without providing any credentials. Use curl or a browser.Affected if The endpoint returns sensitive data or a successful HTTP response without authentication (no 401 or 403 error)
-
Check network exposure of web adminReview firewall rules, network ACLs, or VPN configurations to determine if the Verysync web interface (default port 8886) is accessible from untrusted networks or the public internet.Affected if Port 8886 (or configured web admin port) is exposed to untrusted networks or the internet
A user is affected if Verysync with web admin enabled is accessible and the /rest/f/api/resources/f96956469e7be39d endpoint returns data without authentication.
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 dataSince the vendor did not respond to early disclosure and no patch is available, organizations should restrict network access to the web administration interface (e.g., via firewall rules or VPN), disable the web admin if not required, and monitor for signs of exploitation.
- 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-14197 — 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-14197 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