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

CVE-2026-13252

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-02
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 7 weeks old

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 RSS Aggregator by Feedzy – Feed to Post, Autoblogging, News & YouTube Video Feeds Aggregator plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'aspectRatio' Attribute in all versions up to, and including, 5.2.1 due to insufficient input sanitization and output 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 Feedzy RSS Aggregator WordPress plugin has a stored XSS vulnerability in the 'aspectRatio' attribute. Authenticated users with contributor-level access can inject arbitrary JavaScript through insufficiently sanitized input that is not properly escaped on output, causing the malicious script to execute whenever users access affected pages.

MitigationUpdate the Feedzy plugin to version 5.2.2 or later to obtain the patched version with proper input sanitization and output escaping. Until then, restrict contributor-level user permissions or disable the plugin if immediate patching is not feasible.

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. Verify Feedzy RSS Aggregator plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Feedzy RSS Aggregator' in the installed plugins list, or query the wp_plugins database table for plugin slug containing 'feedzy'
    Affected if The plugin is installed and active
  2. Check installed Feedzy version
    In WordPress admin > Plugins, find Feedzy and note the version number displayed, or query wp_options for option_name 'feedzy_version' or similar version record
    Affected if Version is lower than 5.2.2 (the patched version)
  3. Identify users with contributor-level or higher access
    Navigate to WordPress admin > Users and review user roles, or query wp_usermeta for users with meta_key 'wp_capabilities' containing 'contributor', 'author', 'editor', or 'administrator'
    Affected if Any user account exists with contributor-level permissions or higher (this enables the attack vector)
  4. Inspect stored aspectRatio configuration for malicious scripts
    Query the WordPress database (wp_postmeta or wp_options depending on plugin storage) for any aspectRatio-related entries, examining values for unusual characters such as <, >, script, javascript:, or event handlers like onload/onerror
    Affected if Any aspectRatio value contains HTML tags, JavaScript code, or suspicious event handlers

You are affected if Feedzy RSS Aggregator plugin versions below 5.2.2 are installed and active, contributor-level or higher user accounts exist, AND suspicious aspectRatio values with script injection are present in your database.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Feedzy plugin to version 5.2.2 or later to obtain the patched version with proper input sanitization and output escaping. Until then, restrict contributor-level user permissions or disable the plugin if immediate patching is not feasible.

Recommended fix Moderate confidence

Update to the latest version of RSS Aggregator by Feedzy (version higher than 5.2.1)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'RSS Aggregator by Feedzy' plugin
  4. Check if the current version is 5.2.1 or below
  5. If vulnerable, click 'Update Now' to install the latest version
  6. After updating, verify the new version number in the plugins list
  7. Test that the Feedzy functionality works correctly on the site
Caveat Minor: Review Feedzy settings after upgrade to ensure configuration is intact

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13252 — 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-13252 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