# CVE-2014-2579: Cross-site request forgery in n/a

> Remote attackers can hijack administrator sessions to change passwords or trigger database backups, potentially leading to code execution if specific options are enabled.

- **Severity:** High 7.6 (`AV:N/AC:H/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fp83-g5px-h8vv

## What is CVE-2014-2579?

CVE-2014-2579 is a high-severity vulnerability in n/a, published on 25 Apr 2014. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site request forgery (CSRF) vulnerabilities in XCloner Standalone 3.5 and earlier allow remote attackers to hijack the authentication of administrators for requests that (1) change the administrator password via the config task to index2.php or (2) when the enable_db_backup and sql_mem options are enabled, access the database backup functionality via the dbbackup_comp parameter in the generate action to index2.php.  NOTE: vector 2 might be a duplicate of CVE-2014-2340, which is for the XCloner Wordpress plugin.  NOTE: remote attackers can leverage CVE-2014-2996 with vector 2 to execute arbitrary commands.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2014-2579?

It affects 1 product.


Products: Xcloner Xcloner.

## How do I fix CVE-2014-2579?

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

## Is CVE-2014-2579 being exploited?

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

Public exploit code:

- XCloner Standalone 3.5 - Cross-Site Request Forgery (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2020-35948](https://insights.sbomify.com/CVE-2020-35948/): Missing authorization in n/a (critical 9.9)
- [CVE-2020-35950](https://insights.sbomify.com/CVE-2020-35950/): Cross-site request forgery in n/a (critical 9.8)
- [CVE-2014-2996](https://insights.sbomify.com/CVE-2014-2996/): Command injection in n/a (high 7.1)
- [CVE-2014-2340](https://insights.sbomify.com/CVE-2014-2340/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2020-13424](https://insights.sbomify.com/CVE-2020-13424/): The XCloner component before 3.5.4 for Joomla! (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-2579 and fix it if it is affected.

What it is: CVE-2014-2579 is a high-severity vulnerability in n/a, published on 25 Apr 2014. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-2579 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-2014-2579/ (Markdown: https://insights.sbomify.com/CVE-2014-2579/index.md)
```

## Sources

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

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