Overview 70 matches · 8 in Waratek scope · 5 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
70matches
8in Waratek scope11.4%
5protected7.1%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
5
7.1%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
3
4.3%
Outside Waratek scope
0
0.0%
Not applicable
62
88.6%
Withdrawn CVE
0
0.0%
blocked by ARMR today
5
7.1%
partly blocked
0
0.0%
not blocked
65
92.9%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
70
100.0%
split by
peak 24 / year
20041
Not applicable1
High1
not blocked1
No public exploit1
20050
20060
20075
Not applicable5
Medium3
Low2
not blocked5
No public exploit5
20080
20090
20100
20111
Not applicable1
Medium1
not blocked1
No public exploit1
20120
20130
20141
Not applicable1
Medium1
not blocked1
No public exploit1
20150
20160
20174
Protected by Waratek1
No exploit published1
Not applicable2
Critical1
High2
Medium1
blocked by ARMR today1
not blocked3
No public exploit4
20187
Protected by Waratek2
Not applicable5
Critical4
High1
Medium2
blocked by ARMR today2
not blocked5
No public exploit7
20196
Not applicable6
Critical1
High3
Medium2
not blocked6
No public exploit6
202010
No exploit published1
Not applicable9
Critical1
High1
Medium8
not blocked10
No public exploit10
20213
No exploit published1
Not applicable2
High1
Medium1
Low1
not blocked3
No public exploit3
202224
Not applicable24
Critical15
High2
Medium7
not blocked24
No public exploit24
20232
Not applicable2
Critical1
High1
not blocked2
No public exploit2
20240
20255
Protected by Waratek1
Not applicable4
Critical2
High1
Medium2
blocked by ARMR today1
not blocked4
No public exploit5
20261
Protected by Waratek1
High1
blocked by ARMR today1
No public exploit1
200420062008201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2025-48977 | High | 2026-05-28 | Protected by Waratek | No public exploit | Relative Path Traversal vulnerability in Apache Ignite REST API. Authenticated REST API users can read any file on the server with "cmd=log" command and a log path crafted in a certain way. This issue affects Apache Ignite: from 2.0.0 through 2.17.0. Users are recommended to upgrade to version 2.18.0, which fixes the issue. |
| CVE-2025-54418 | Critical | 2025-07-28 | Not applicable | No public exploit | CodeIgniter is a PHP full-stack web framework. A command injection vulnerability present in versions prior to 4.6.2 affects applications that use the ImageMagick handler for image processing (`imagick` as the image library) and either allow file uploads with user-controlled filenames and process uploaded images using the `resize()` method or use the `text()` method with user-controlled text content or options. An attacker can upload a file with a malicious filename containing shell metacharacters that get executed when the image is processed or provide malicious text content or options that get executed when adding text to images Users should upgrade to v4.6.2 or later to receive a patch. As a workaround, switch to the GD image handler (`gd`, the default handler), which is not affected by either vulnerability. For file upload scenarios, instead of using user-provided filenames, generate random names to eliminate the attack vector with `getRandomName()` when using the `move()` method, or use the `store()` method, which automatically generates safe filenames. For text operations, if one must use ImageMagick with user-controlled text, sanitize the input to only allow safe characters and validate/restrict text options. |
| CVE-2024-44314 | Medium | 2025-03-18 | Not applicable | No public exploit | TastyIgniter 3.7.6 contains an Incorrect Access Control vulnerability in the Orders Management System, allowing unauthorized users to update order statuses. The issue occurs in the index_onUpdateStatus() function within Orders.php, which fails to verify if the user has permission to modify an order's status. This flaw can be exploited remotely, leading to unauthorized order manipulation. |
| CVE-2024-44313 | High | 2025-03-18 | Not applicable | No public exploit | TastyIgniter 3.7.6 contains an Incorrect Access Control vulnerability in the invoice() function within Orders.php which allows unauthorized users to access and generate invoices due to missing permission checks. |
| CVE-2024-52577 | Critical | 2025-02-14 | Protected by Waratek | No public exploit | In Apache Ignite versions from 2.6.0 and before 2.17.0, configured Class Serialization Filters are ignored for some Ignite endpoints. The vulnerability could be exploited if an attacker manually crafts an Ignite message containing a vulnerable object whose class is present in the Ignite server classpath and sends it to Ignite server endpoints. Deserialization of such a message by the Ignite server may result in the execution of arbitrary code on the Apache Ignite server side. |
| CVE-2025-24013 | Medium | 2025-01-20 | Not applicable | No public exploit | CodeIgniter is a PHP full-stack web framework. Prior to 4.5.8, CodeIgniter lacked proper header validation for its name and value. The potential attacker can construct deliberately malformed headers with Header class. This could disrupt application functionality, potentially causing errors or generating invalid HTTP requests. In some cases, these malformed requests might lead to a DoS scenario if a remote service’s web application firewall interprets them as malicious and blocks further communication with the application. This vulnerability is fixed in 4.5.8. |
| CVE-2023-46240 | High | 2023-10-31 | Not applicable | No public exploit | CodeIgniter is a PHP full-stack web framework. Prior to CodeIgniter4 version 4.4.3, if an error or exception occurs, a detailed error report is displayed even if in the production environment. As a result, confidential information may be leaked. Version 4.4.3 contains a patch. As a workaround, replace `ini_set('display_errors', '0')` with `ini_set('display_errors', 'Off')` in `app/Config/Boot/production.php`. |
| CVE-2023-32692 | Critical | 2023-05-30 | Not applicable | No public exploit | CodeIgniter is a PHP full-stack web framework. This vulnerability allows attackers to execute arbitrary code when you use Validation Placeholders. The vulnerability exists in the Validation library, and validation methods in the controller and in-model validation are also vulnerable because they use the Validation library internally. This issue is patched in version 4.3.5. |
| CVE-2022-46170 | Critical | 2022-12-22 | Not applicable | No public exploit | CodeIgniter is a PHP full-stack web framework. When an application uses (1) multiple session cookies (e.g., one for user pages and one for admin pages) and (2) a session handler is set to `DatabaseHandler`, `MemcachedHandler`, or `RedisHandler`, then if an attacker gets one session cookie (e.g., one for user pages), they may be able to access pages that require another session cookie (e.g., for admin pages). This issue has been patched, please upgrade to version 4.2.11 or later. As a workaround, use only one session cookie. |
| CVE-2022-23556 | High | 2022-12-22 | Not applicable | No public exploit | CodeIgniter is a PHP full-stack web framework. This vulnerability may allow attackers to spoof their IP address when the server is behind a reverse proxy. This issue has been patched, please upgrade to version 4.2.11 or later, and configure `Config\App::$proxyIPs`. As a workaround, do not use `$request->getIPAddress()`. |
| CVE-2022-40835 | Critical | 2022-10-07 | Not applicable | No public exploit | B.C. Institute of Technology CodeIgniter <=3.1.13 is vulnerable to SQL Injection via system\database\DB_query_builder.php. Note: Multiple third parties have disputed this as not a valid vulnerability |
| CVE-2022-40834 | Critical | 2022-10-07 | Not applicable | No public exploit | B.C. Institute of Technology CodeIgniter <=3.1.13 is vulnerable to SQL Injection via system\database\DB_query_builder.php or_not_like() function. Note: Multiple third parties have disputed this as not a valid vulnerability. |
| CVE-2022-40833 | Critical | 2022-10-07 | Not applicable | No public exploit | B.C. Institute of Technology CodeIgniter <=3.1.13 is vulnerable to SQL Injection via system\database\DB_query_builder.php or_where_in() function. Note: Multiple third parties have disputed this as not a valid vulnerability. |
| CVE-2022-40832 | Critical | 2022-10-07 | Not applicable | No public exploit | B.C. Institute of Technology CodeIgniter <=3.1.13 is vulnerable to SQL Injection via system\database\DB_query_builder.php having() function. Note: Multiple third parties have disputed this as not a valid vulnerability. |
| CVE-2022-40831 | Critical | 2022-10-07 | Not applicable | No public exploit | B.C. Institute of Technology CodeIgniter <=3.1.13 is vulnerable to SQL Injection via system\database\DB_query_builder.php like() function. Note: Multiple third parties have disputed this as not a valid vulnerability. |
| CVE-2022-40830 | Critical | 2022-10-07 | Not applicable | No public exploit | B.C. Institute of Technology CodeIgniter <=3.1.13 is vulnerable to SQL Injection via system\database\DB_query_builder.php where_not_in() function. Note: Multiple third parties have disputed this as not a valid vulnerability. |
| CVE-2022-40829 | Critical | 2022-10-07 | Not applicable | No public exploit | B.C. Institute of Technology CodeIgniter <=3.1.13 is vulnerable to SQL Injection via system\database\DB_query_builder.php or_like() function. Note: Multiple third parties have disputed this as not a valid vulnerability. |
| CVE-2022-40828 | Critical | 2022-10-07 | Not applicable | No public exploit | B.C. Institute of Technology CodeIgniter <=3.1.13 is vulnerable to SQL Injection via system\database\DB_query_builder.php or_where_not_in() function. Note: Multiple third parties have disputed this as not a valid vulnerability. |
| CVE-2022-40827 | Critical | 2022-10-07 | Not applicable | No public exploit | B.C. Institute of Technology CodeIgniter <=3.1.13 is vulnerable to SQL Injection via system\database\DB_query_builder.php where() function. Note: Multiple third parties have disputed this as not a valid vulnerability. |
| CVE-2022-40826 | Critical | 2022-10-07 | Not applicable | No public exploit | B.C. Institute of Technology CodeIgniter <=3.1.13 is vulnerable to SQL Injection via system\database\DB_query_builder.php or_having() function. Note: Multiple third parties have disputed this as not a valid vulnerability. |
| CVE-2022-40825 | Critical | 2022-10-07 | Not applicable | No public exploit | B.C. Institute of Technology CodeIgniter <=3.1.13 is vulnerable to SQL Injection via system\database\DB_query_builder.php where_in() function. Note: Multiple third parties have disputed this as not a valid vulnerability. |
| CVE-2022-40824 | Critical | 2022-10-07 | Not applicable | No public exploit | B.C. Institute of Technology CodeIgniter <=3.1.13 is vulnerable to SQL Injection via system\database\DB_query_builder.php or_where() function. Note: Multiple third parties have disputed this as not a valid vulnerability. |
| CVE-2022-38256 | Medium | 2022-09-08 | Not applicable | No public exploit | TastyIgniter v3.5.0 was discovered to contain a cross-site scripting (XSS) vulnerability which allows attackers to execute arbitrary web scripts or HTML via a crafted payload. |
| CVE-2022-35213 | Medium | 2022-08-18 | Not applicable | No public exploit | Ecommerce-CodeIgniter-Bootstrap before commit 56465f was discovered to contain a cross-site scripting (XSS) vulnerability via the function base_url() at /blog/blogpublish.php. |
| CVE-2022-0898 | Medium | 2022-05-09 | Not applicable | No public exploit | The IgniteUp WordPress plugin through 3.4.1 does not sanitise and escape some fields when high privilege users don't have the unfiltered_html capability, which could lead to Stored Cross-Site Scripting issues |
| CVE-2022-26624 | Medium | 2022-04-08 | Not applicable | No public exploit | Bootstrap v3.1.11 and v3.3.7 was discovered to contain a cross-site scripting (XSS) vulnerability via the Title parameter in /vendor/views/add_product.php. |
| CVE-2022-0602 | Medium | 2022-04-05 | Not applicable | No public exploit | Cross-site Scripting (XSS) - DOM in GitHub repository tastyigniter/tastyigniter prior to 3.3.0. |
| CVE-2022-24712 | High | 2022-02-28 | Not applicable | No public exploit | CodeIgniter4 is the 4.x branch of CodeIgniter, a PHP full-stack web framework. A vulnerability in versions prior to 4.1.9 might allow remote attackers to bypass the CodeIgniter4 Cross-Site Request Forgery (CSRF) protection mechanism. Users should upgrade to version 4.1.9. There are workarounds for this vulnerability, but users will still need to code as these after upgrading to v4.1.9. Otherwise, the CSRF protection may be bypassed. If auto-routing is enabled, check the request method in the controller method before processing. If auto-routing is disabled, either avoid using `$routes->add()` and instead use HTTP verbs in routes; or check the request method in the controller method before processing. |
| CVE-2022-24711 | Critical | 2022-02-28 | Not applicable | No public exploit | CodeIgniter4 is the 4.x branch of CodeIgniter, a PHP full-stack web framework. Prior to version 4.1.9, an improper input validation vulnerability allows attackers to execute CLI routes via HTTP request. Version 4.1.9 contains a patch. There are currently no known workarounds for this vulnerability. |
| CVE-2022-23378 | Medium | 2022-02-09 | Not applicable | No public exploit | A Cross-Site Scripting (XSS) vulnerability exists within the 3.2.2 version of TastyIgniter. The "items%5B0%5D%5Bpath%5D" parameter of a request made to /admin/allergens/edit/1 is vulnerable. |
| CVE-2022-21715 | Medium | 2022-01-24 | Not applicable | No public exploit | CodeIgniter4 is the 4.x branch of CodeIgniter, a PHP full-stack web framework. A cross-site scripting (XSS) vulnerability was found in `API\ResponseTrait` in Codeigniter4 prior to version 4.1.8. Attackers can do XSS attacks if a potential victim is using `API\ResponseTrait`. Version 4.1.8 contains a patch for this vulnerability. There are two potential workarounds available. Users may avoid using `API\ResponseTrait` or `ResourceController` Users may also disable Auto Route and use defined routes only. |
| CVE-2022-21647 | Critical | 2022-01-04 | Not applicable | No public exploit | CodeIgniter is an open source PHP full-stack web framework. Deserialization of Untrusted Data was found in the `old()` function in CodeIgniter4. Remote attackers may inject auto-loadable arbitrary objects with this vulnerability, and possibly execute existing PHP code on the server. We are aware of a working exploit, which can lead to SQL injection. Users are advised to upgrade to v4.1.6 or later. Users unable to upgrade as advised to not use the `old()` function and form_helper nor `RedirectResponse::withInput()` and `redirect()->withInput()`. |
| CVE-2021-40975 | Medium | 2021-10-01 | Not applicable | No public exploit | Cross-site scripting (XSS) vulnerability in application/modules/admin/views/ecommerce/products.php in Ecommerce-CodeIgniter-Bootstrap (Codeigniter 3.1.11, Bootstrap 3.3.7) allows remote attackers to inject arbitrary web script or HTML via the search_title parameter. |
| CVE-2020-18694 | High | 2021-08-06 | Not applicable | No public exploit | Cross Site Request Forgery (CSRF) in IgnitedCMS v1.0 allows remote attackers to obtain sensitive information and gain privilege via the component "/admin/profile/save_profile". |
| CVE-2021-28163 | Low | 2021-04-01 | No exploit published | No public exploit | In Eclipse Jetty 9.4.32 to 9.4.38, 10.0.0.beta2 to 10.0.1, and 11.0.0.beta2 to 11.0.1, if a user uses a webapps directory that is a symlink, the contents of the webapps directory is deployed as a static webapp, inadvertently serving the webapps themselves and anything else that might be in that directory. |
| CVE-2020-25093 | Medium | 2020-09-03 | Not applicable | No public exploit | Ecommerce-CodeIgniter-Bootstrap before 2020-08-03 allows XSS in blog.php. within application/views/templates/clothesshop, application/views/templates/onepage, and application/views/templates/redlabel. |
| CVE-2020-25092 | Medium | 2020-09-03 | Not applicable | No public exploit | Ecommerce-CodeIgniter-Bootstrap before 2020-08-03 allows XSS in _parts/header.php, within application/views/templates/clothesshop, application/views/templates/greenlabel, and application/views/templates/redlabel. |
| CVE-2020-25091 | Medium | 2020-09-03 | Not applicable | No public exploit | Ecommerce-CodeIgniter-Bootstrap before 2020-08-03 allows XSS in application/modules/vendor/views/add_product.php. |
| CVE-2020-25090 | Medium | 2020-09-03 | Not applicable | No public exploit | Ecommerce-CodeIgniter-Bootstrap before 2020-08-03 allows XSS in application/modules/admin/views/ecommerce/publish.php. |
| CVE-2020-25089 | Medium | 2020-09-03 | Not applicable | No public exploit | Ecommerce-CodeIgniter-Bootstrap before 2020-08-03 allows XSS in application/modules/admin/views/ecommerce/discounts.php. |
| CVE-2020-25088 | Medium | 2020-09-03 | Not applicable | No public exploit | Ecommerce-CodeIgniter-Bootstrap before 2020-08-03 allows XSS in application/modules/admin/views/blog/blogpublish.php. |
| CVE-2020-25087 | Medium | 2020-09-03 | Not applicable | No public exploit | Ecommerce-CodeIgniter-Bootstrap before 2020-08-03 allows XSS in application/modules/admin/views/advanced_settings/languages.php. |
| CVE-2020-25086 | Medium | 2020-09-03 | Not applicable | No public exploit | Ecommerce-CodeIgniter-Bootstrap before 2020-08-03 allows XSS in application/modules/admin/views/advanced_settings/adminUsers.php. |
| CVE-2020-1963 | Critical | 2020-06-03 | No exploit published | No public exploit | Apache Ignite uses H2 database to build SQL distributed execution engine. H2 provides SQL functions which could be used by attacker to access to a filesystem. |
| CVE-2020-10793 | High | 2020-03-23 | Not applicable | No public exploit | CodeIgniter through 4.0.0 allows remote attackers to gain privileges via a modified Email ID to the "Select Role of the User" page. NOTE: A contributor to the CodeIgniter framework argues that the issue should not be attributed to CodeIgniter. Furthermore, the blog post reference shows an unknown website built with the CodeIgniter framework but that CodeIgniter is not responsible for introducing this issue because the framework has never provided a login screen, nor any kind of login or user management facilities beyond a Session library. Also, another reporter indicates the issue is with a custom module/plugin to CodeIgniter, not CodeIgniter itself. |
| CVE-2019-17237 | High | 2019-11-12 | Not applicable | No public exploit | includes/class-coming-soon-creator.php in the igniteup plugin through 3.4 for WordPress allows CSRF. |
| CVE-2019-17236 | Medium | 2019-11-12 | Not applicable | No public exploit | includes/class-coming-soon-creator.php in the igniteup plugin through 3.4 for WordPress is vulnerable to stored XSS. |
| CVE-2019-17235 | Medium | 2019-11-12 | Not applicable | No public exploit | includes/class-coming-soon-creator.php in the igniteup plugin through 3.4 for WordPress allows information disclosure. |
| CVE-2019-17234 | High | 2019-11-12 | Not applicable | No public exploit | includes/class-coming-soon-creator.php in the igniteup plugin through 3.4 for WordPress allows unauthenticated arbitrary file deletion. |
| CVE-2019-13370 | High | 2019-07-06 | Not applicable | No public exploit | index.php/admin/permissions in Ignited CMS through 2017-02-19 allows CSRF to add an administrator. |
| CVE-2015-3907 | Critical | 2019-07-03 | Not applicable | No public exploit | CodeIgniter Rest Server (aka codeigniter-restserver) 2.7.1 allows XXE attacks. |
| CVE-2018-15203 | Medium | 2018-08-08 | Not applicable | No public exploit | An issue was discovered in Ignited CMS through 2017-02-19. ign/index.php/admin/pages/add_page allows a CSRF attack to add pages. |
| CVE-2018-8018 | Critical | 2018-07-20 | Protected by Waratek | No public exploit | In Apache Ignite before 2.4.8 and 2.5.x before 2.5.3, the serialization mechanism does not have a list of classes allowed for serialization/deserialization, which makes it possible to run arbitrary code when 3-rd party vulnerable classes are present in Ignite classpath. The vulnerability can be exploited if the one sends a specially prepared form of a serialized object to GridClientJdkMarshaller deserialization endpoint. |
| CVE-2018-12071 | Critical | 2018-06-17 | Not applicable | No public exploit | A Session Fixation issue exists in CodeIgniter before 3.1.9 because session.use_strict_mode in the Session Library was mishandled. |
| CVE-2016-10552 | High | 2018-05-31 | Not applicable | No public exploit | igniteui 0.0.5 and earlier downloads JavaScript and CSS resources over insecure protocol. |
| CVE-2018-1295 | Critical | 2018-04-02 | Protected by Waratek | No public exploit | In Apache Ignite 2.3 or earlier, the serialization mechanism does not have a list of classes allowed for serialization/deserialization, which makes it possible to run arbitrary code when 3-rd party vulnerable classes are present in Ignite classpath. The vulnerability can be exploited if the one sends a specially prepared form of a serialized object to one of the deserialization endpoints of some Ignite components - discovery SPI, Ignite persistence, Memcached endpoint, socket steamer. |
| CVE-2015-5725 | Critical | 2018-02-21 | Not applicable | No public exploit | SQL injection vulnerability in the offset method in the Active Record class in CodeIgniter before 2.2.4 allows remote attackers to execute arbitrary SQL commands via vectors involving the offset variable. |
| CVE-2013-4891 | Medium | 2018-02-21 | Not applicable | No public exploit | The xss_clean function in CodeIgniter before 2.1.4 might allow remote attackers to bypass an intended protection mechanism and conduct cross-site scripting (XSS) attacks via an unclosed HTML tag. |
| CVE-2017-1000247 | High | 2017-11-17 | Not applicable | No public exploit | British Columbia Institute of Technology CodeIgniter 3.1.3 is vulnerable to HTTP Header Injection in the set_status_header() common function under Apache resulting in HTTP Header Injection flaws. |
| CVE-2017-7686 | High | 2017-06-28 | No exploit published | No public exploit | Apache Ignite 1.0.0-RC3 to 2.0 uses an update notifier component to update the users about new project releases that include additional functionality, bug fixes and performance improvements. To do that the component communicates to an external PHP server (http://ignite.run) where it needs to send some system properties like Apache Ignite or Java version. Some of the properties might contain user sensitive information. |
| CVE-2016-6805 | Medium | 2017-04-07 | Protected by Waratek | No public exploit | Apache Ignite before 1.9 allows man-in-the-middle attackers to read arbitrary files via XXE in modified update-notifier documents. |
| CVE-2016-10131 | Critical | 2017-01-12 | Not applicable | No public exploit | system/libraries/Email.php in CodeIgniter before 3.1.3 allows remote attackers to execute arbitrary code by leveraging control over the email->from field to insert sendmail command-line arguments. |
| CVE-2014-6951 | Medium | 2014-10-15 | Not applicable | No public exploit | The OneFile Ignite (aka uk.co.onefile.ignite) application 1.19 for Android does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate. |
| CVE-2011-3719 | Medium | 2011-09-23 | Not applicable | No public exploit | CodeIgniter 1.7.2 allows remote attackers to obtain sensitive information via a direct request to a .php file, which reveals the installation path in an error message, as demonstrated by system/scaffolding/views/view.php and certain other files. |
| CVE-2007-4590 | Low | 2007-08-29 | Not applicable | No public exploit | The get_system_info command in Ignite-UX C.7.0 through C.7.3, and DynRootDisk (DRD) A.1.0.16.417 through A.2.0.0.592, on HP-UX B.11.11, B.11.23, and B.11.31 does not inform local users of networking changes made by the command, which has unknown impact and attack vectors. |
| CVE-2007-3709 | Medium | 2007-07-11 | Not applicable | No public exploit | CRLF injection vulnerability in the redirect function in url_helper.php in CodeIgniter 1.5.3 allows remote attackers to inject arbitrary HTTP headers via CRLF sequences in an unspecified parameter, as demonstrated by a Set-Cookie header. |
| CVE-2007-3708 | Medium | 2007-07-11 | Not applicable | No public exploit | Cross-site scripting (XSS) vulnerability in CodeIgniter 1.5.3 before 20070626 allows remote attackers to inject arbitrary web script or HTML via (1) String.fromCharCode and (2) malformed nested tag manipulations in an unspecified component, related to insufficient sanitization by the xss_clean function. |
| CVE-2007-3707 | Medium | 2007-07-11 | Not applicable | No public exploit | Directory traversal vulnerability in index.php in CodeIgniter 1.5.3 before 20070628, when enable_query_strings is true, allows remote attackers to read arbitrary files via a .. (dot dot) in the c parameter. |
| CVE-2007-3706 | Low | 2007-07-11 | Not applicable | No public exploit | The _sanitize_globals function in CodeIgniter 1.5.3 before 20070628 allows remote attackers to unset arbitrary global variables with unspecified impact, as demonstrated by a _SERVER cookie. |
| CVE-2004-0951 | High | 2004-12-31 | Not applicable | No public exploit | The make_recovery command for the TFTP server in HP Ignite-UX before C.6.2.241 makes a copy of the password file in the TFTP directory tree, which allows remote attackers to obtain sensitive information. |