# CVE-2025-27294: WordPress WP-Asambleas plugin <= 2.85.0 - Arbitrary Shortcode Execution vulnerability

> Attackers can execute arbitrary shortcodes due to missing authorization checks in the WP-Asambleas plugin.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/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:** 24 Feb 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-h7xh-jqw8-mhx8

## What is CVE-2025-27294?

CVE-2025-27294 is a medium-severity missing authorization vulnerability in platcom WP-Asambleas, published on 24 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing Authorization vulnerability in platcom WP-Asambleas wp-asambleas allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP-Asambleas: from n/a through <= 2.85.0.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-27294 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-27294 is a medium-severity missing authorization vulnerability in platcom WP-Asambleas, published on 24 Feb 2025. 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-2025-27294 in the wild and no public exploit code.

Affected product: platcom WP-Asambleas. 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-27294/ (Markdown: https://insights.sbomify.com/CVE-2025-27294/index.md)
```

## Sources

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

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