Advanced Category TemplateWordPress extension · Praveengoswami
CVE-2023-50835
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Praveen Goswami Advanced Category Template.This issue affects Advanced Category Template: from n/a through 0.1.
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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the Advanced Category Template plugin allows attackers to trick authenticated users into performing unintended actions, such as modifying category templates or settings, by exploiting the lack of proper request validation.
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
Advanced Category TemplateWordPress extension
<= 0.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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Verify plugin is installedNavigate to WordPress admin > Plugins and confirm 'Advanced Category Template' by Praveengoswami is installed and activeAffected if Plugin is present and active in the WordPress installation
-
Check installed versionIn Plugins list, look at the version column for Advanced Category Template, or view the plugin header in its main PHP file (typically wp-content/plugins/advanced-category-template/advanced-category-template.php)Affected if Version is 0.1 or lower, or version cannot be determined (indicating outdated or altered version)
-
Inspect admin action handlers for nonce validationExamine the main plugin PHP file for state-changing functions (category template updates, settings changes). Search for absence of wp_nonce_field, wp_nonce_url, check_admin_referer, or wp_verify_nonce calls before any insert/update/delete operationsAffected if No nonce verification is found before database changes or settings modifications in the plugin code
-
Check form submissions for token presenceReview plugin code for any HTML forms that submit to admin-post.php or admin-ajax.php. Verify if these forms include nonce input fields (wp_nonce_field)Affected if Forms that modify settings or templates lack hidden nonce token fields
-
Verify Origin/Referer header validationSearch plugin code for $_SERVER['HTTP_ORIGIN'] or $_SERVER['HTTP_REFERER'] validation logic in action handlersAffected if No server-side validation of request origin is implemented
If the Advanced Category Template plugin version 0.1 or lower is installed and its code lacks nonce verification on state-changing operations, the environment is vulnerable to CVE-2023-50835.
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 dataImplement anti-CSRF tokens (nonce validation) for all state-changing operations and verify Origin/Referer headers to ensure requests originate from legitimate sources.
Fix this in Advanced Category Template
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50835 — 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-2023-50835 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