# CVE-2025-63739: Missing authorization in n/a

> Authenticated attackers can modify PHP configuration files in RockOA, potentially leading to code execution or system compromise.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** 9 Dec 2025
- **Updated:** 11 Dec 2025
- **Also known as:** GHSA-jjcj-frhf-qphh

## What is CVE-2025-63739?

CVE-2025-63739 is a medium-severity missing authorization vulnerability in n/a, published on 9 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in function phpinisaveAction in file webmain/system/cogini/coginiAction.php in Xinhu Rainrock RockOA 2.7.0 allowing attackers to authenticated users to modify PHP configuration files via the a parameter to the index.php endpoint.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-63739?

It affects 1 product.


Products: Rockoa Rockoa.

## How do I fix CVE-2025-63739?

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

## Is CVE-2025-63739 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-63742](https://insights.sbomify.com/CVE-2025-63742/): SQL injection in n/a (critical 9.8)
- [CVE-2023-49363](https://insights.sbomify.com/CVE-2023-49363/): SQL injection in n/a (critical 9.8)
- [CVE-2020-18713](https://insights.sbomify.com/CVE-2020-18713/): SQL injection in n/a (critical 9.8)
- [CVE-2020-18714](https://insights.sbomify.com/CVE-2020-18714/): SQL injection in n/a (critical 9.8)
- [CVE-2020-18716](https://insights.sbomify.com/CVE-2020-18716/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-63739 and fix it if it is affected.

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

## Sources

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

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