dbcve.org
Ahmeti Wp TimelineWordPress extension · Ahmetimamoglu

CVE-2024-49237

MEDIUM · 6.1 CVSS v3.1 Published 2024-10-17
Fix available
A fix is available. Upgrade to after 5.1 or later.
See remediation →
68/100
Remediation priority · Elevated
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 ahmeti Ahmeti Wp Timeline ahmeti-wp-timeline allows Stored XSS.This issue affects Ahmeti Wp Timeline: from n/a through <= 5.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 confidence

A CSRF vulnerability in the Ahmeti Wp Timeline WordPress plugin (versions up to 5.1) allows attackers to trick authenticated administrators into submitting malicious requests that result in Stored XSS. The lack of proper CSRF token validation on state-changing operations enables attackers to craft requests that execute arbitrary JavaScript in the context of the affected site.

MitigationAdd anti-CSRF tokens (nonces) to all forms and AJAX actions that modify timeline data, and implement proper input sanitization and output encoding to prevent the XSS payload from being stored and executed.

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
Ahmeti Wp TimelineWordPress extension
Affected:<= 5.1

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

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

  1. Confirm Ahmeti Wp Timeline plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Ahmeti Wp Timeline' by Ahmetimamoglu, or check the plugin files in /wp-content/plugins/ directory for the ahmeti-wp-timeline folder
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    In WordPress admin > Plugins > Installed Plugins, click 'View Details' on Ahmeti Wp Timeline to see the version number, or open the main plugin file (e.g., ahmeti-wp-timeline.php) and check the plugin header comment for the Version field
    Affected if The version is 5.1 or lower (including any version listed without a version number in older releases)
  3. Verify presence of timeline data that could be exploited
    Check if the plugin has created any timeline entries - typically accessible via a timeline post type in the WordPress admin (look for a menu item like 'Timeline', 'WP Timeline', or custom post type added by the plugin)
    Affected if There are timeline entries present in the database that could be manipulated via CSRF
  4. Inspect state-changing admin forms for CSRF protection
    Access any admin page that allows creating or editing timeline entries. View the page source or inspect form HTML to look for a wpnonce, _wpnonce, or CSRF token field in forms that submit to the plugin
    Affected if Forms that modify timeline data lack a nonce token (no field like '_wpnonce', 'nonce', or 'security' is present in the form HTML)
  5. Check AJAX actions for CSRF token validation
    Use browser developer tools to monitor network requests when saving timeline data via AJAX. Examine the request payload for a nonce parameter, and if possible, test whether the request succeeds when the nonce is removed
    Affected if AJAX requests that modify timeline data do not require a valid nonce parameter to succeed

If the Ahmeti Wp Timeline plugin version 5.1 or lower is installed AND forms/AJAX actions that modify timeline data lack CSRF token validation, the environment is vulnerable to CVE-2024-49237.

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.

From vendor data
Upgrade available Upgrade to a release after 5.1
Interim mitigation

Add anti-CSRF tokens (nonces) to all forms and AJAX actions that modify timeline data, and implement proper input sanitization and output encoding to prevent the XSS payload from being stored and executed.

Fix this in Ahmeti Wp Timeline 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-2024-49237 — 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-49237 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