NewspaperWordPress extension · Tagdiv
CVE-2021-3135
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 · uneditedAn issue was discovered in the tagDiv Newspaper theme 10.3.9.1 for WordPress. It allows XSS via the wp-admin/admin-ajax.php td_block_id parameter in a td_ajax_block API call.
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 confidenceA reflected Cross-Site Scripting (XSS) vulnerability exists in the tagDiv Newspaper WordPress theme version 10.3.9.1. The vulnerability stems from insufficient sanitization of the td_block_id parameter passed to the wp-admin/admin-ajax.php endpoint via the td_ajax_block API call, allowing attackers to inject malicious JavaScript code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
NewspaperWordPress extension
= 10.3.9.1CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed theme and versionNavigate to Appearance > Themes in WordPress admin, or inspect the style.css file in wp-content/themes/newspaper/ to find the 'Version' headerAffected if The theme is tagDiv Newspaper version 10.3.9.1 exactly
-
Verify the AJAX endpoint is accessibleSend a GET or POST request to /wp-admin/admin-ajax.php?action=td_ajax_block and confirm the endpoint respondsAffected if The endpoint returns a valid response indicating the td_ajax_block functionality is active
-
Test the td_block_id parameter for XSS reflectionSend a request to admin-ajax.php with a crafted td_block_id value containing a test payload such as <script>alert(1)</script> and observe if it is reflected unescaped in the responseAffected if The malicious payload is reflected in the response without proper encoding or sanitization
If the Newspaper theme version is exactly 10.3.9.1 and the td_block_id parameter in the td_ajax_block AJAX call reflects unsanitized input, the environment is affected by CVE-2021-3135.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the tagDiv Newspaper theme to the latest patched version. If immediate updating is not feasible, implement a Web Application Firewall (WAF) rule to filter malicious payloads in the td_block_id parameter, or disable the vulnerable td_ajax_block functionality until the patch can be applied.
Fix this in Newspaper
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-3135 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-3135 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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