dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-49313

HIGH · 7.1 CVSS v3.1 Published 2024-10-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 rudestan VKontakte Wall Post vkontakte-wall-post allows Stored XSS.This issue affects VKontakte Wall Post: from n/a through <= 2.0.

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

CSRF vulnerability in the VKontakte Wall Post WordPress plugin allows attackers to craft malicious requests that, when executed by an authenticated administrator, inject and persistently store malicious JavaScript (Stored XSS) into the plugin's output. The attack exploits the lack of anti-CSRF tokens on state-changing forms.

MitigationApply vendor-supplied patch or update to latest version; implement CSRF tokens (nonces) on all state-changing operations and output escaping on stored data.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Identify if the VKontakte Wall Post plugin is installed
    Navigate to WordPress admin > Plugins > Installed Plugins and search for 'VKontakte Wall Post' or 'vkontakte' in the plugin list. Alternatively, check the /wp-content/plugins/ directory for a folder containing 'vkontakte' or 'vk' in the name.
    Affected if The plugin is present in the WordPress installation
  2. Determine the installed plugin version
    In WordPress admin > Plugins, find the VKontakte Wall Post plugin and locate the version number displayed below the plugin name. Compare this to any available changelog or release notes to assess if it includes the fix.
    Affected if The installed version predates the security patch (version unknown; check vendor release notes for patch date)
  3. Verify if the plugin is active on the site
    In WordPress admin > Plugins, confirm the VKontakte Wall Post plugin shows as 'Active'. Only active plugins process requests and are vulnerable.
    Affected if The plugin is currently activated and processing requests
  4. Inspect plugin source code for missing CSRF nonce verification
    Access the plugin files via FTP or file manager. Examine PHP files handling form submissions (typically in the main plugin file or includes/admin/). Search for 'wp_nonce_field', 'wp_nonce_url', or 'check_admin_referer' functions on state-changing operations like settings saves or wall post submissions.
    Affected if State-changing form handlers lack nonce verification functions
  5. Check for stored XSS vulnerabilities in plugin output
    Review plugin PHP files for output functions that echo stored data (options, post content, user input) without using escaping functions like esc_html(), esc_attr(), or esc_url(). Particularly examine areas where plugin settings or wall post content are displayed in the admin dashboard or frontend.
    Affected if User-supplied or stored data is output without proper escaping

The environment is affected if the VKontakte Wall Post plugin is installed, active, and its source code shows missing nonce verification on state-changing forms or unescaped stored data output.

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

Apply vendor-supplied patch or update to latest version; implement CSRF tokens (nonces) on all state-changing operations and output escaping on stored data.

Recommended fix Moderate confidence

Latest version of VKontakte Wall Post (vkontakte-wall-post) plugin (version higher than 2.0)

  1. 1. Check the WordPress admin dashboard for available updates to the VKontakte Wall Post (vkontakte-wall-post) plugin
  2. 2. If an update is available, navigate to Plugins > Installed Plugins > VKontakte Wall Post
  3. 3. Click 'Update Now' to install the latest patched version of the plugin
  4. 4. After updating, verify the plugin is functioning correctly and test that CSRF protections are in place

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

Have this fixed 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 help mitigating

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-2024-49313 — 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-2024-49313 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