dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-4025

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The PrivateContent Free plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'align' shortcode attribute in the [pc-login-form] shortcode in all versions up to, and including, 1.2.0. This is due to insufficient input sanitization and output escaping on the 'align' attribute. Specifically, the attribute value flows from the shortcode through pc_login_form() to pc_static::form_align(), where it is directly concatenated into an HTML class attribute without esc_attr() or any escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The PrivateContent Free WordPress plugin up to version 1.2.0 contains a stored XSS vulnerability in the [pc-login-form] shortcode. The 'align' attribute is not sanitized or escaped, flowing directly from the shortcode handler through pc_login_form() to pc_static::form_align() where it is concatenated into an HTML class attribute without esc_attr(). Attackers with Contributor-level access can inject arbitrary JavaScript.

MitigationApply esc_attr() to the 'align' attribute value when outputting it in the HTML class attribute, and add input validation/sanitization (such as in_array() with allowed values) in the shortcode handler to restrict the attribute to safe values.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin version
    Navigate to WordPress dashboard > Plugins > PrivateContent Free and check the installed version. Compare against the affected range (versions up to and including 1.2.0).
    Affected if Installed version is 1.2.0 or lower.
  2. Locate shortcode usage
    Search WordPress posts, pages, and widget content for the string '[pc-login-form' to find all instances where this shortcode is used.
    Affected if Any instance of the [pc-login-form] shortcode exists on the site.
  3. Identify align attribute usage
    Examine each [pc-login-form] shortcode occurrence for the 'align' attribute (e.g., [pc-login-form align="..."]). Check post/page content, custom post types, or template files where shortcodes may be embedded.
    Affected if The align attribute is present in any shortcode usage.
  4. Inspect vulnerable function code
    Access the plugin source files via FTP or file manager. Locate the file containing pc_static::form_align() (typically in includes/classes folder). Open the file and inspect the form_align method to verify if esc_attr() is applied to the align value before output in the HTML class attribute.
    Affected if The form_align function does not use esc_attr() or htmlspecialchars() on the align parameter before outputting it into the HTML class attribute.
  5. Verify contributor+ access exists
    Review user accounts in WordPress admin under Users section. Check for any accounts with Contributor, Author, Editor, or Administrator roles.
    Affected if At least one user account with Contributor-level access or higher exists on the site.

The site is affected if PrivateContent Free plugin version 1.2.0 or lower is installed, the [pc-login-form] shortcode with an align attribute is in use, and the form_align() function lacks output escaping on the align value.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply esc_attr() to the 'align' attribute value when outputting it in the HTML class attribute, and add input validation/sanitization (such as in_array() with allowed values) in the shortcode handler to restrict the attribute to safe values.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4025 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4025 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data