dbcve.org
Smarty For WordpressWordPress extension · Presspage

CVE-2023-37992

HIGH · 8.8 CVSS v3.1 Published 2023-10-03
Fix available
A fix is available. Upgrade to after 3.1.35 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in PressPage Entertainment Inc. Smarty for WordPress plugin <= 3.1.35 versions.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Smarty for WordPress plugin versions 3.1.35 and below allows attackers to trick authenticated administrators into performing unintended actions, such as modifying plugin settings or injecting malicious content, by forcing their browser to send crafted requests.

MitigationUpdate the Smarty for WordPress plugin to the latest version once available; alternatively, implement anti-CSRF tokens (nonces) on all state-changing operations within the plugin.

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
Smarty For WordpressWordPress extension
Affected:<= 3.1.35

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
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 checks

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

  1. Confirm Smarty for WordPress plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Presspage Smarty For Wordpress' or 'Smarty for WordPress' in the list
    Affected if The plugin appears in the installed plugins list
  2. Check the installed plugin version
    In the installed plugins list, click on the plugin or look for the version number displayed under the plugin name. Alternatively, access the plugin files via FTP or file manager and check the main plugin PHP file for the 'Version' header in the plugin comment block
    Affected if The version listed is 3.1.35 or any version lower (e.g., 3.1.34, 3.1.0, etc.)
  3. Identify state-changing operations in the plugin
    Examine the plugin source code for form submissions or URL requests that modify settings, content, or plugin behavior. Look for PHP files handling admin actions, settings pages, or content injection points. Common patterns include $_POST, $_GET, or $_REQUEST handling without nonce verification
    Affected if The plugin processes state-changing requests (such as saving settings, updating content, or modifying configuration) without verifying a nonce token or CSRF token

You are affected if the Presspage Smarty For Wordpress plugin is installed with version 3.1.35 or lower and the plugin performs administrative actions without anti-CSRF token validation.

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
Upgrade available Upgrade to a release after 3.1.35
Interim mitigation

Update the Smarty for WordPress plugin to the latest version once available; alternatively, implement anti-CSRF tokens (nonces) on all state-changing operations within the plugin.

Recommended fix Moderate confidence

Smarty for WordPress version 3.1.36 or later

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Locate 'Smarty for WordPress' in the plugin list
  5. 5. Check if an update is available for the plugin
  6. 6. If an update is available, click 'Update Now' to install the latest version
  7. 7. After updating, verify the plugin is functioning correctly on your site
  8. 8. Test critical functionalities that depend on Smarty for WordPress

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

Fix this in Smarty For Wordpress Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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