Web
CVE-2025-69080
PHP Local File Inclusion via include/require in JanStudio Gecko <=1.9.8
- CVSS
- 8.1Highscored by the publisher (CNA)
- Exploited in the wild
- Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
- EPSS
- 0.48%chance of exploitation in the next 30 daystop 58% of scored CVEsFIRST score of 13 Nov 2026
- Fix
- Not stated by the vendorno fixed release in the CVE record
- Published
- 7 Jan 2026analysed here 7 Jan 2026
Summary
Impact
LFI via PHP include/require enables attacker to read sensitive local files and configs; may lead to code execution in permissive environments.
Triage
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| JanStudio Gecko | <= 1.9.8Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- JanStudio Gecko <= 1.9.8
Fix and mitigation
Action required
Patch when possible
WAF and other mitigations
Can a WAF block it? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.
Also consider: patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept
- CISA SSVC
- exploitation none, automatable no, technical impact totalAssessed by CISA 7 Jan 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
GitHub proofs of concept
- AndrielSec/CVE-2025-690800 stars
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 7 Jan 2026Analysed by vulneraibility.com
- 7 Jan 2026Published1 day later
- 7 Jan 2026CISA SSVC assessment: exploitation nonesame day later
- 28 Apr 2026CVE record last updated111 days (about 4 months) later
- 31 Aug 2026First proof-of-concept repository on GitHub (unvetted)124 days (about 4 months) later
Common questions
Is CVE-2025-69080 being exploited?
Not confirmed. CVE-2025-69080 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.48% probability of exploitation in the next 30 days.
How severe is CVE-2025-69080?
CVE-2025-69080 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-69080?
Not known from our data. No patch reference has been recorded for CVE-2025-69080, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2025-69080 affect?
CVE-2025-69080 affects JanStudio Gecko <= 1.9.8. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2025-69080?
Upgrade Gecko to patched version when available
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
1 reference in the CVE record, grouped by the tags the record gives them.
Other links (1)
- patchstack.com /database/Wordpress/Theme/gecko/vulnerability/wordpress-gecko-theme-1-9-8-local-
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.