CVE-2025-2117
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 Beijing Founder Electronics Founder Enjoys All-Media Acquisition and Editing System 3.0 and classified as critical. Affected by this issue is the function electricDocList of the file /newsedit/report/reportCenter.do. The manipulation of the argument fvID/catID leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public 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 · high confidenceSQL injection vulnerability in Beijing Founder Electronics Founder Enjoys All-Media Acquisition and Editing System 3.0. The electricDocList function in /newsedit/report/reportCenter.do fails to properly sanitize the fvID and catID parameters, allowing attackers to inject malicious SQL queries remotely. Public exploit available.
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.
-
Identify if Founder Enjoys All-Media Acquisition and Editing System is installedReview installed software inventory or check for the product's web directory on the server. Look for application directories containing 'founder' or 'enjoys' in the web root path.Affected if The system is running Beijing Founder Electronics Founder Enjoys All-Media Acquisition and Editing System
-
Check the installed version numberLocate version information in system configuration files, about pages, or the application's main interface. Common paths include version metadata files in the web application directory or the system administration panel.Affected if The version is 3.0 (or falls within the 3.x line without the vendor patch)
-
Verify the affected endpoint is accessibleAttempt to access the URL path /newsedit/report/reportCenter.do on the web server. Check if the endpoint responds (even with an error) to confirm the application module is present.Affected if The endpoint returns an HTTP response, indicating the vulnerable module is exposed
-
Confirm the electricDocList function is exposedReview application routing configuration or attempt a request to the endpoint with the electricDocList action parameter. Check if the function handler is registered and accessible.Affected if The electricDocList function is registered and reachable without authentication
If the system runs Founder Enjoys All-Media Acquisition and Editing System version 3.0 with the /newsedit/report/reportCenter.do endpoint and electricDocList function exposed, it is likely vulnerable to CVE-2025-2117.
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 parameterized queries or prepared statements for the electricDocList function to sanitize fvID/catID inputs; apply input validation and consider WAF rules as temporary mitigation pending vendor patch.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2117 — 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-2117 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