CVE-2015-3224

NONECVSS 0.0Weaponized
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 45%CVSS: —Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

request.rb in Web Console before 2.1.3, as used with Ruby on Rails 3.x and 4.x, does not properly restrict the use of X-Forwarded-For headers in determining a client's IP address, which allows remote attackers to bypass the whitelisted_ips protection mechanism via a crafted request.

CVSS v3
—
EG Score
0.0(none)
EG Risk
0
EG Risk 0/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses intrinsic severity with real-world exploitation and automatability, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. It is distinct from the 0–10 EG Score, which measures severity.

EPSS
98.7%
KEV
Not listed

Published

July 26, 2015

Last Modified

May 6, 2026

References (10)

Affected Packages

(1 across 1 ecosystem)
RubyGems(1)
PackageVulnerable rangeFixed inDependents
web-console0.1.0 ... 2.1.2 (17 versions)2.1.3—

Data Freshness Timeline

(refreshed 12× in last 7d / 33× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-23 01:17 UTCEG score recompute▼ 2.50
  2. 2026-07-23 00:19 UTCEG score recompute▲ 2.50
  3. 2026-07-22 21:58 UTCEG score recompute▼ 9.00
  4. 2026-07-22 14:04 UTCEPSS rescore
  5. 2026-07-21 15:21 UTCEPSS rescore
  6. 2026-07-21 15:21 UTCEPSS rescore
  7. 2026-07-20 17:03 UTCEPSS rescore
  8. 2026-07-19 14:27 UTCEPSS rescore
  9. 2026-07-19 14:27 UTCEPSS rescore
  10. 2026-07-18 10:00 UTCEPSS rescore
  11. 2026-07-16 16:59 UTCEPSS rescore
  12. 2026-07-16 16:59 UTCEPSS rescore
  13. 2026-07-15 16:54 UTCEPSS rescore
  14. 2026-07-15 16:54 UTCEPSS rescore
  15. 2026-07-15 01:56 UTCEPSS rescore
  16. 2026-07-13 22:26 UTCEPSS rescore
  17. 2026-07-12 05:42 UTCEPSS rescore
  18. 2026-07-11 08:23 UTCEPSS rescore
  19. 2026-07-09 19:05 UTCEPSS rescore
  20. 2026-07-08 15:10 UTCEPSS rescore
  21. 2026-07-06 16:24 UTCEPSS rescore
  22. 2026-07-05 02:26 UTCEPSS rescore
  23. 2026-07-04 06:27 UTCEPSS rescore
  24. 2026-07-02 15:21 UTCEPSS rescore
  25. 2026-07-01 15:02 UTCEPSS rescore
Show 47 more
  1. 2026-07-01 15:02 UTCEPSS rescore
  2. 2026-06-28 04:53 UTCEPSS rescore
  3. 2026-06-27 03:05 UTCEPSS rescore
  4. 2026-06-25 13:47 UTCEPSS rescore
  5. 2026-06-25 13:47 UTCEPSS rescore
  6. 2026-06-24 14:02 UTCEPSS rescore
  7. 2026-06-24 14:02 UTCEPSS rescore
  8. 2026-06-23 21:30 UTCEPSS rescore
  9. 2026-06-22 14:23 UTCEPSS rescore
  10. 2026-06-22 14:22 UTCEPSS rescore
  11. 2026-06-21 14:54 UTCEPSS rescore
  12. 2026-06-21 01:57 UTCEPSS rescore
  13. 2026-06-21 01:57 UTCEPSS rescore
  14. 2026-06-18 17:50 UTCEPSS rescore
  15. 2026-06-18 17:49 UTCEPSS rescore
  16. 2026-06-17 17:49 UTCEPSS rescore
  17. 2026-06-16 17:50 UTCEPSS rescore
  18. 2026-06-16 17:49 UTCEPSS rescore
  19. 2026-06-15 17:45 UTCEPSS rescore
  20. 2026-06-12 23:09 UTCEPSS rescore
  21. 2026-06-10 22:15 UTCEPSS rescore
  22. 2026-06-08 14:14 UTCEPSS rescore
  23. 2026-06-06 13:45 UTCEPSS rescore
  24. 2026-06-05 22:44 UTCEPSS rescore
  25. 2026-06-05 06:08 UTCEPSS rescore
  26. 2026-06-05 06:08 UTCEPSS rescore
  27. 2026-06-04 13:10 UTCEPSS rescore
  28. 2026-06-04 13:09 UTCEPSS rescore
  29. 2026-05-31 22:28 UTCEPSS rescore
  30. 2026-05-31 22:28 UTCEPSS rescore
  31. 2026-05-31 22:28 UTCEPSS rescore
  32. 2026-05-31 00:14 UTCEPSS rescore
  33. 2026-05-29 13:41 UTCEPSS rescore
  34. 2026-05-28 13:42 UTCEPSS rescore
  35. 2026-05-28 13:42 UTCEPSS rescore
  36. 2026-05-26 07:16 UTCEPSS rescore
  37. 2026-05-26 07:16 UTCEPSS rescore
  38. 2026-05-24 16:43 UTCEPSS rescore
  39. 2026-05-23 15:10 UTCEPSS rescore
  40. 2026-05-23 00:22 UTCEG score recompute
  41. 2026-05-22 21:15 UTCEPSS rescore
  42. 2026-05-22 21:15 UTCEPSS rescore
  43. 2026-05-21 22:40 UTCEPSS rescore
  44. 2026-05-20 22:37 UTCEPSS rescore
  45. 2026-05-20 22:37 UTCEPSS rescore
  46. 2026-05-18 21:30 UTCEPSS rescore
  47. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(5 references)

Working exploit code is in the public domain (1 Metasploit module) (2 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoC0xEval/cve-2015-3224
    First seen May 3, 2018

    Ruby on Rails Web Console (v2) Whitelist Bypass Code Execution implementation in Python

    Open source ↗
  • GitHub PoC0x00-0x00/CVE-2015-3224
    First seen Feb 8, 2018

    Modification of Metasploit module for RCE in Ruby-On-Rails Console CVE-2015-3224

    Open source ↗
  • Exploit-DBEDB-41689✓ verified
    First seen Jun 16, 2015

    Ruby on Rails 4.0.x/4.1.x/4.2.x (Web Console v2) - Whitelist Bypass Code Execution (Metasploit)

    Open source ↗
  • Metasploitexploit/multi/http/rails_web_console_v2_code_exec✓ verified
    First seen Jun 16, 2015

    Ruby on Rails Web Console (v2) Whitelist Bypass Code Execution

    Open source ↗
  • Nucleihttp/cves/2015/CVE-2015-3224.yaml
    First seen Jan 1, 2015

    Ruby on Rails Web Console - Remote Code Execution

    Open source ↗

Frequently asked(4)

What is CVE-2015-3224?
CVE-2015-3224 is a none vulnerability published on July 26, 2015. request.rb in Web Console before 2.1.3, as used with Ruby on Rails 3.x and 4.x, does not properly restrict the use of X-Forwarded-For headers in determining a client's IP address, which allows remote attackers to bypass the whitelisted_ips protection mechanism via a crafted request.
When was CVE-2015-3224 disclosed?
CVE-2015-3224 was first published in the National Vulnerability Database on July 26, 2015, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2015-3224 actively exploited?
CVE-2015-3224 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2015-3224?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2015-3224, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2015-3224

Explore →

Is Your Infrastructure Affected by CVE-2015-3224?

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

Start Free Scan →Browse All CVEs