How severe is CVE-2012-5699?

CVE-2012-5699 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2012-5699 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 5% (91st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2012-5699?

CVE-2012-5699 affects Babygekko. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2012-5699?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2012-5699 published?

CVE-2012-5699 was published on 2020-01-23 and last updated on 2026-06-16.

CVE-2012-5699

CVE-2012-5699 is a critical-severity vulnerability in Babygekko with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-20.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
CVSS v2: 7.5
EPSS exploit prediction: 5% (91st percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-20
Affected product: Babygekko
Published: 2020-01-23
Last modified: 2026-06-16

Description

BabyGekko before 1.2.4 allows PHP file inclusion.

Frequently asked questions

What is CVE-2012-5699?: BabyGekko before 1.2.4 allows PHP file inclusion.
How severe is CVE-2012-5699?: CVE-2012-5699 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2012-5699 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 5% (91st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2012-5699?: CVE-2012-5699 affects Babygekko. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2012-5699?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2012-5699 published?: CVE-2012-5699 was published on 2020-01-23 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:babygekko:babygekko:*:*:*:*:*:*:*:*

More vulnerabilities in Babygekko

CVE-2012-5698 — High (CVSS 8.8): BabyGekko before 1.2.4 has SQL injection.

All CVEs affecting Babygekko →

Other CWE-20 (Improper Input Validation) vulnerabilities

CVE-2026-48316 — Critical (CVSS 10.0): ColdFusion versions 2025.9, 2023.20 and earlier are affected by an Improper Input Validation vulnerability that could…
CVE-2026-48281 — Critical (CVSS 10.0): ColdFusion versions 2025.9, 2023.20 and earlier are affected by an Improper Input Validation vulnerability that could…
CVE-2026-48277 — Critical (CVSS 10.0): ColdFusion versions 2025.9, 2023.20 and earlier are affected by an Improper Input Validation vulnerability that could…
CVE-2026-48055 — Critical (CVSS 10.0): Streambert is a cross-platform Electron Desktop App to stream and download any video media. In versions 2.4.0 and…
CVE-2026-34910 — Critical (CVSS 10.0): A malicious actor with access to the network could exploit an Improper Input Validation vulnerability found in UniFi OS…
CVE-2026-33587 — Critical (CVSS 10.0): Lack of user input sanitisation in Open Notebook v1.8.3 allows the application user to execute Python code (and…

Browse all CWE-20 (Improper Input Validation) vulnerabilities →