CVE-2007-5216 Multiple PHP remote file inclusion vulnerabilities in eArk (e-Ark) 1.0 allow remote attackers to execute arbitrary PHP code via a URL in (1)
Medium 6.8
Published
Updated
Check this codebase for CVE-2007-5216 and fix it if it is affected.
What it is: CVE-2007-5216 is a medium-severity vulnerability in n/a, published on 4 Oct 2007.
Exploitation: There is no known exploitation of CVE-2007-5216 in the wild and no public exploit code.
Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2007-5216/ (Markdown: https://insights.sbomify.com/CVE-2007-5216/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2007-5216?
CVE-2007-5216 is a medium-severity vulnerability in n/a, published on 4 Oct 2007.
Official description
Multiple PHP remote file inclusion vulnerabilities in eArk (e-Ark) 1.0 allow remote attackers to execute arbitrary PHP code via a URL in (1) the cfg_vcard_path parameter to src/vcard_inc.php or (2) the cfg_phpmailer_path parameter to src/email_inc.php. NOTE: the ark_inc.php vector is already covered by CVE-2006-6086.
Weakness: CWE-94
Which versions are affected by CVE-2007-5216?
It affects 1 product.
Products include E-Ark E-Ark.
How do I fix CVE-2007-5216?
No fix has been published for CVE-2007-5216 yet. Limit exposure of the affected software until one is available.
Is CVE-2007-5216 being exploited?
There is no known exploitation of CVE-2007-5216 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-gc98-v57j-w56g.