# CVE-2003-0249: Security feature bypass in n/a

> Attackers can bypass Apache method-based access controls by using non-standard HTTP methods, as PHP treats them as GET requests.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Feb 2006
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-xc5f-pfpm-hrw6

## What is CVE-2003-0249?

CVE-2003-0249 is a high-severity vulnerability in Php Php, published on 27 Feb 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PHP treats unknown methods such as "PoSt" as a GET request, which could allow attackers to intended access restrictions if PHP is running on a server that passes on all methods, such as Apache httpd 2.0, as demonstrated using a Limit directive.  NOTE: this issue has been disputed by the Apache security team, saying "It is by design that PHP allows scripts to process any request method.  A script which does not explicitly verify the request method will hence be processed as normal for arbitrary methods.  It is therefore expected behaviour that one cannot implement per-method access control using the Apache configuration alone, which is the assumption made in this report.

## Which versions are affected by CVE-2003-0249?

It affects 1 product.


Products: Php Php.

## How do I fix CVE-2003-0249?

No fix has been published for CVE-2003-0249 yet. Limit exposure of the affected software until one is available.

## Is CVE-2003-0249 being exploited?

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

## Other vulnerabilities in Php Php

- [CVE-2012-2688](https://insights.sbomify.com/CVE-2012-2688/): Integer overflow in n/a (critical 10.0)
- [CVE-2012-2376](https://insights.sbomify.com/CVE-2012-2376/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-3268](https://insights.sbomify.com/CVE-2011-3268/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-4143](https://insights.sbomify.com/CVE-2009-4143/): Other in n/a (critical 10.0)
- [CVE-2008-5557](https://insights.sbomify.com/CVE-2008-5557/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0249 and fix it if it is affected.

What it is: CVE-2003-0249 is a high-severity vulnerability in Php Php, published on 27 Feb 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-0249 in the wild and no public exploit code.

Affected product: Php Php. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2003-0249/ (Markdown: https://insights.sbomify.com/CVE-2003-0249/index.md)
```

## Sources

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

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