CVE-2025-7103
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 BoyunCMS up to 1.4.20. It has been rated as critical. This issue affects some unknown processing of the file /application/pay/controller/Index.php of the component curl. The manipulation leads to server-side request forgery. The attack may be initiated remotely. The exploit has been disclosed to the public 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 · high confidenceBoyunCMS versions up to 1.4.20 contain a server-side request forgery (SSRF) vulnerability in the /application/pay/controller/Index.php file via the curl component. The vulnerability allows remote attackers to induce the server to make arbitrary requests to internal or external resources by manipulating input to the curl functionality.
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.4, <= 1.4.20CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Locate Boyuncms installationSearch for the presence of the /application/pay/controller/Index.php file in the web root directory, or look for Boyuncms-specific directory structure.Affected if The file /application/pay/controller/Index.php exists in the web application directory.
-
Determine installed Boyuncms versionCheck for a version file or metadata in the Boyuncms installation (such as a version.php, composer.json, or README file). Compare the found version against the affected range of 1.4 through 1.4.20.Affected if The installed version is 1.4 or higher, up to and including 1.4.20.
-
Verify the vulnerable curl component existsExamine the /application/pay/controller/Index.php file and confirm it contains curl functionality (look for curl_init, curl_exec, or similar curl-related PHP functions).Affected if The Index.php file in the pay controller contains curl request handling code.
-
Check if pay module is accessibleDetermine whether the pay controller is accessible via web requests by checking routing configuration or attempting to access the /pay or /index.php/pay endpoint.Affected if The pay module is routable and accessible via HTTP requests without authentication.
A system is affected if Boyuncms version 1.4 through 1.4.20 is installed, the vulnerable /application/pay/controller/Index.php file with curl functionality exists, and the pay module is accessible.
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 and allowlisting for all outbound requests in the affected curl component, restricting requests to trusted domains only and blocking requests to internal network resources.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7103 — 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-7103 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