CVE-2007-2774

UNRATEDCVSS · not yet scoredWeaponized
—
EchelonGraph verdictPlan mitigationWithin your standard update timelines — no confirmed exploitation yet.
  • Public exploit code is available (Exploit-DB, marked verified by Exploit-DB)
CISA-KEV: Not listedEPSS PROB: 3.7%CVSS v2: —Exploit: Exploit-DB (verified)Exposed services: Not assessed

No fix has been recorded since the CVE record was published in 2007 — if the vendor still supports the product, apply the fixed version it names; if not, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Multiple PHP remote file inclusion vulnerabilities in SunLight CMS 5.3 allow remote attackers to execute arbitrary PHP code via a URL in the root parameter to (1) _connect.php or (2) modules/startup.php.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
3.7%
EPSS %ILE
89th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
3.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 21, 2007

Last Modified

August 7, 2024

References (7)

Data Freshness Timeline

(refreshed 8× in last 7d / 27× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-23 16:25 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  2. 2026-10-22 16:25 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  3. 2026-10-21 16:25 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  4. 2026-10-20 16:25 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  5. 2026-10-19 16:25 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  6. 2026-10-18 16:25 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  7. 2026-10-18 11:59 UTCEG score recompute
  8. 2026-10-17 16:25 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  9. 2026-10-16 16:25 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  10. 2026-10-15 16:25 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  11. 2026-10-14 16:25 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  12. 2026-10-13 16:25 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  13. 2026-10-12 21:58 UTCEG score recompute
  14. 2026-10-12 16:26 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  15. 2026-10-12 02:07 UTCEG score recompute
  16. 2026-10-11 13:37 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  17. 2026-10-10 19:53 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  18. 2026-10-09 20:00 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  19. 2026-10-08 16:33 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  20. 2026-10-07 23:37 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  21. 2026-10-06 15:09 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  22. 2026-10-05 17:37 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  23. 2026-10-04 23:15 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  24. 2026-10-03 14:20 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  25. 2026-10-01 19:42 UTCEPSS rescoreEPSS 3.7% · 89th percentile
Show 21 more
  1. 2026-09-30 14:57 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  2. 2026-09-29 07:41 UTCEG score recompute
  3. 2026-09-18 19:20 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  4. 2026-09-17 19:20 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  5. 2026-09-15 03:04 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  6. 2026-09-12 14:54 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  7. 2026-09-05 15:22 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  8. 2026-09-04 13:55 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  9. 2026-09-04 04:59 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  10. 2026-08-30 01:14 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  11. 2026-08-08 16:30 UTCEPSS rescoreEPSS 3.7% · 88th percentile
  12. 2026-08-07 16:20 UTCEPSS rescoreEPSS 3.7% · 88th percentile
  13. 2026-08-06 13:41 UTCEPSS rescoreEPSS 3.7% · 88th percentile
  14. 2026-08-05 19:11 UTCEPSS rescoreEPSS 3.7% · 88th percentile
  15. 2026-08-04 15:03 UTCEPSS rescoreEPSS 3.7% · 88th percentile
  16. 2026-08-03 10:28 UTCEPSS rescoreEPSS 3.7% · 88th percentile
  17. 2026-07-30 16:22 UTCEPSS rescoreEPSS 3.7% · 88th percentile
  18. 2026-07-30 01:25 UTCEPSS rescoreEPSS 3.7% · 88th percentile
  19. 2026-07-28 15:30 UTCEPSS rescoreEPSS 3.7% · 88th percentile
  20. 2026-07-27 12:57 UTCEG score recompute
  21. 2026-07-27 12:57 UTCGHSA enrichmentGHSA-wqh3-26vv-cwq2 · GitHub severity HIGH

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Exploit-DB entry). No fix has been recorded since the CVE record was published in 2007. If the vendor still supports the product, apply the fixed version it names; if it no longer does, isolate the affected system or retire the product.

  • Exploit-DBEDB-3953✓ verified
    Published May 19, 2007

    SunLight CMS 5.3 - 'root' Remote File Inclusion

    Open source ↗

Frequently asked(4)

What is CVE-2007-2774?
CVE-2007-2774 is a vulnerability whose severity is not yet rated; its CVE record was published on May 21, 2007. Multiple PHP remote file inclusion vulnerabilities in SunLight CMS 5.3 allow remote attackers to execute arbitrary PHP code via a URL in the root parameter to (1) _connect.php or (2) modules/startup.php.
When was CVE-2007-2774 made public?
CVE-2007-2774 was made public on May 19, 2007: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on May 21, 2007. EchelonGraph's copy of the record carries a last-modified date of August 7, 2024; the record at its source may have been updated since.
Is CVE-2007-2774 actively exploited?
CVE-2007-2774 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: Exploit-DB marks a public exploit for it as verified. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 3.7% probability of exploitation in the next 30 days (89th percentile of EPSS-scored CVEs).
How do I remediate CVE-2007-2774?
No fix for CVE-2007-2774 has been recorded since its CVE record was published in 2007. If the vendor still supports the product, apply the fixed version it names; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2007-2774

Explore →

Is Your Infrastructure Affected by CVE-2007-2774?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs