How severe is GHSA-mwjc-5j4x-r686?

GHSA-mwjc-5j4x-r686 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-mwjc-5j4x-r686?

GHSA-mwjc-5j4x-r686 affects the following packages: wwbn/avideo (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-mwjc-5j4x-r686?

No patched version of wwbn/avideo has shipped for GHSA-mwjc-5j4x-r686 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-mwjc-5j4x-r686 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wwbn/avideo. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-mwjc-5j4x-r686 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-mwjc-5j4x-r686?

O3 pinpoints whether GHSA-mwjc-5j4x-r686 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-mwjc-5j4x-r686 actively exploited in the wild?

No public exploit code has been indexed for GHSA-mwjc-5j4x-r686 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-mwjc-5j4x-r686?

GHSA-mwjc-5j4x-r686 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 14th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-mwjc-5j4x-r686?

GHSA-mwjc-5j4x-r686 is classified as Improper Authentication (CWE-287), CWE-312 (CWE-312), CWE-326 (CWE-326), Broken Cryptographic Algorithm (CWE-327). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-mwjc-5j4x-r686 published, and has it been updated?

GHSA-mwjc-5j4x-r686 was published on March 20, 2026 and was last updated on March 25, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-mwjc-5j4x-r686

HIGH

AVideo has an unauthenticated decrypt oracle leaking any ciphertext

Also known asCVE-2026-33512

Published

Mar 20, 2026

Updated

Mar 25, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk14th percentile+0.19%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐘wwbn/avideo

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Summary

The API plugin exposes a decryptString action without any authentication. Anyone can submit ciphertext and receive plaintext. Ciphertext is issued publicly (e.g., view/url2Embed.json.php), so any user can recover protected tokens/metadata. Severity: High.

Details

Entry: plugin/API/get.json.php is unauthenticated.
Handler: plugin/API/API.php get_api_decryptString() (lines ~5945–5966):
```
$string = decryptString($_REQUEST['string']);
return new ApiObject($string, empty($string));
```
No APISecret or user check occurs before decrypting.
Public ciphertext source: view/url2Embed.json.php returns playLink/playEmbedLink (encryptString(json_encode(...))) to any caller.

PoC

Obtain ciphertext:

GET /view/url2Embed.json.php?url=https://example.com/video.mp4

Copy playLink.

Decrypt without auth:

POST /plugin/API/get.json.php?APIName=decryptString
Content-Type: application/x-www-form-urlencoded

string=<playLink ciphertext>

Response contains the plaintext JSON (videoLink, title, users_id, etc.).

Impact

Any encrypted payload produced by the platform can be decrypted by anyone.
Leaks tokens/links intended to be confidential; enables replay and tampering where secrecy was assumed.

Mitigation

Require API secret or authenticated/authorized user for decryptString, or remove the endpoint.
Prefer one-way signatures (HMAC) instead of exposing generic decryption.
Rotate encryption keys/salts after patch to invalidate exposed ciphertexts.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`wwbn/avideo`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wwbn/avideo. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Remediation status
No patched version of wwbn/avideo has shipped for GHSA-mwjc-5j4x-r686 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-mwjc-5j4x-r686 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-mwjc-5j4x-r686. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary The API plugin exposes a `decryptString` action without any authentication. Anyone can submit ciphertext and receive plaintext. Ciphertext is issued publicly (e.g., `view/url2Embed.json.php`), so any user can recover protected tokens/metadata. Severity: High. ### Details - Entry: `plugin/API/get.json.php` is unauthenticated. - Handler: `plugin/API/API.php` `get_api_decryptString()` (lines ~5945–5966): ```php $string = decryptString($_REQUEST['string']); return new ApiObject($string, empty($string)); ``` No APISecret or user check occurs before decrypting. - Public cipher

O3 Security · Impact-Aware SCA

Is GHSA-mwjc-5j4x-r686 in your dependencies?

O3 detects GHSA-mwjc-5j4x-r686 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works