# CVE-2015-9456: Missing authorization in n/a

> An attacker can modify theme files without proper authorization due to incorrect access control in the Orbisius Child Theme Creator plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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:** No
- **Published:** 7 Oct 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9q39-xwg9-4fvm

## What is CVE-2015-9456?

CVE-2015-9456 is a medium-severity missing authorization vulnerability in n/a, published on 7 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The orbisius-child-theme-creator plugin before 1.2.8 for WordPress has incorrect access control for file modification via the wp-admin/admin-ajax.php?action=orbisius_ctc_theme_editor_ajax&sub_cmd=save_file theme_1, theme_1_file, or theme_1_file_contents parameter.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2015-9456?

It affects 1 product.


Products: Orbisius Child Theme Creator.

## How do I fix CVE-2015-9456?

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

## Is CVE-2015-9456 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-28649](https://insights.sbomify.com/CVE-2020-28649/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2024-43276](https://insights.sbomify.com/CVE-2024-43276/): WordPress Child Theme Creator by Orbisius plugin <= 1.5.4 - Cross Site Scripting (XSS) vulnerability (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-9456 and fix it if it is affected.

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

## Sources

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

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