# CVE-2011-3993: Missing authorization in n/a

> Remote authenticated users can modify files and settings in Movable Type plugins due to weak permissions.

- **Severity:** Medium 5.5 (`AV:N/AC:L/Au:S/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Nov 2011
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-rrj5-x37f-2q48

## What is CVE-2011-3993?

CVE-2011-3993 is a medium-severity missing authorization vulnerability in n/a, published on 3 Nov 2011. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SKYARC MTCMS before 5.252, and the MultiFileUploader 0.44 and earlier, DuplicateEntry 1.2 and earlier, MailPack 1.741 and earlier, and AutoTagging 0.08 and earlier plugins for Movable Type, uses weak permissions, which allows remote authenticated users to modify files and settings via unspecified vectors.

Weakness: CWE-264

## Which versions are affected by CVE-2011-3993?

It affects 5 products.


Products: Skyarc Autotagging, Skyarc Duplicateentry, Skyarc Mailpack, Skyarc Mtcms, Skyarc Multifileuploader.

## How do I fix CVE-2011-3993?

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

## Is CVE-2011-3993 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-3994](https://insights.sbomify.com/CVE-2011-3994/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-3993 and fix it if it is affected.

What it is: CVE-2011-3993 is a medium-severity missing authorization vulnerability in n/a, published on 3 Nov 2011. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-3993 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-2011-3993/ (Markdown: https://insights.sbomify.com/CVE-2011-3993/index.md)
```

## Sources

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

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