# CVE-2013-4594: Missing authorization in n/a

> Remote anonymous users can exploit missing access restrictions to use other users' payments when submitting forms in the Drupal Payment for Webform module.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-rxh2-8r9g-2mg2

## What is CVE-2013-4594?

CVE-2013-4594 is a medium-severity missing authorization vulnerability in n/a, published on 25 Oct 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Payment for Webform module 7.x-1.x before 7.x-1.5 for Drupal does not restrict access by anonymous users, which allows remote anonymous users to use the payment of other anonymous users when submitting a form that requires payment.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Payment for Webform Project Payment for Webform.

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

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

## Is CVE-2013-4594 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-4594 is a medium-severity missing authorization vulnerability in n/a, published on 25 Oct 2014. 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-2013-4594 in the wild and no public exploit code.

Affected product: n/a. 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-2013-4594/ (Markdown: https://insights.sbomify.com/CVE-2013-4594/index.md)
```

## Sources

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

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