# CVE-2013-0276: ActiveRecord vulnerable to modification of protected model attributes

> Remote attackers can bypass attribute protection in Ruby on Rails ActiveRecord to modify protected model attributes via crafted requests.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Feb 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-0276, GHSA-gr44-7grc-37vq

## What is CVE-2013-0276?

CVE-2013-0276 is a medium-severity missing authorization vulnerability in Rubyonrails Rails, published on 13 Feb 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ActiveRecord in Ruby on Rails before 2.3.17, 3.1.x before 3.1.11, and 3.2.x before 3.2.12 allows remote attackers to bypass the attr_protected protection mechanism and modify protected model attributes via a crafted request.

Weakness: CWE-264

## Which versions are affected by CVE-2013-0276?

6 open source packages ship an affected version, including activerecord. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `activerecord` | RubyGems | All versions | 2.3.17 |
| `activerecord` | RubyGems | All versions | 2.3.17 |
| `activerecord` | RubyGems | From 3.1.0 | 3.1.11 |
| `activerecord` | RubyGems | From 3.1.0 | 3.1.11 |
| `activerecord` | RubyGems | From 3.2.0 | 3.2.12 |
| `activerecord` | RubyGems | From 3.2.0 | 3.2.12 |

Products: Rubyonrails Rails.

## How do I fix CVE-2013-0276?

Upgrade activerecord to a fixed version for your release line: 2.3.17, 3.1.11 or 3.2.12.

## Is CVE-2013-0276 being exploited?

There is no known exploitation of CVE-2013-0276 in the wild and no public exploit code.

## Other vulnerabilities in Rubyonrails Rails

- [CVE-2013-0277](https://insights.sbomify.com/CVE-2013-0277/): Active Record contains deserialization of arbitrary YAML (critical 10.0)
- [CVE-2017-17916](https://insights.sbomify.com/CVE-2017-17916/): SQL injection in n/a (high 8.1)
- [CVE-2017-17917](https://insights.sbomify.com/CVE-2017-17917/): SQL injection in n/a (high 8.1)
- [CVE-2026-33195](https://insights.sbomify.com/CVE-2026-33195/): Rails Active Storage has possible Path Traversal in DiskService (high 8.0)
- [CVE-2024-26142](https://insights.sbomify.com/CVE-2024-26142/): Rails possible ReDoS vulnerability in Accept header parsing in Action Dispatch (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-0276 and fix it if it is affected.

What it is: CVE-2013-0276 is a medium-severity missing authorization vulnerability in Rubyonrails Rails, published on 13 Feb 2013. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-0276 in the wild and no public exploit code.

Affected packages and fixed versions:
- activerecord (RubyGems): affected all versions; fixed in 2.3.17
- activerecord (RubyGems): affected all versions; fixed in 2.3.17
- activerecord (RubyGems): affected from 3.1.0; fixed in 3.1.11
- activerecord (RubyGems): affected from 3.1.0; fixed in 3.1.11
- activerecord (RubyGems): affected from 3.2.0; fixed in 3.2.12
- activerecord (RubyGems): affected from 3.2.0; fixed in 3.2.12

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-0276/ (Markdown: https://insights.sbomify.com/CVE-2013-0276/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-0276
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-0276
- OSV: https://osv.dev/vulnerability/CVE-2013-0276

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-0276/
Summaries are generated and may contain mistakes; the official description above is the record.