ContentStudio: A security weakness

ContentStudio is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation.

CVE / CNA score 9.8 CVSS 3.1 · security@wordfence.com

NVD score 6.5 CVSS 3.1 · nvd@nist.gov

Component: ContentStudio
Plugin slug: contentstudio
Affected: See vendor advisory
Safe version: See mitigation notes
Published: Jan 27, 2023
Weakness: CWE-862 — Missing Authorization

This CVE was published Jan 27, 2023 and is one of 8 known issues for this plugin.

What to do

Update, patch or deactivate.

Update ContentStudio to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

The ContentStudio plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on several functions in versions up to, and including, 1.2.5. This makes it possible for unauthenticated attackers to obtain the blog metadata (via the function cstu_get_metadata) that includes the plugin's contentstudio_token. Knowing this token allows for other interactions with the plugin such as creating posts in versions prior to 1.2.5, which added other requirements to posting and updating.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

NVD vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

References

Update, patch or deactivate.

Technical description

Primary and upstream sources