dbcve.org
Pexels\Application · Raajtram

CVE-2024-25915

HIGH · 8.8 CVSS v3.1 Published 2024-02-23
Fix available
A fix is available. Upgrade to after 1.2.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Server-Side Request Forgery (SSRF) vulnerability in Raaj Trambadia Pexels: Free Stock Photos.This issue affects Pexels: Free Stock Photos: from n/a through 1.2.2.

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

Server-Side Request Forgery (SSRF) vulnerability in the Pexels WordPress plugin versions up to 1.2.2 allows attackers to induce the server to make arbitrary HTTP requests to attacker-controlled or internal destinations, potentially accessing internal services, cloud metadata endpoints, or bypassing network restrictions.

MitigationImplement strict URL allowlisting and validate all user-supplied URLs before making server-side requests, restricting destinations to trusted domains only; disable unnecessary URL protocols and ensure proper input sanitization.

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
Pexels\Application
Affected:<= 1.2.2

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 Pexels plugin installation
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and locate 'Pexels' by Raajtram
    Affected if The Raajtram Pexels plugin is present in the WordPress installation
  2. Verify plugin version
    In the Plugins list, find the Pexels plugin version column or click on the plugin to view details
    Affected if Installed version is 1.2.2 or lower
  3. Check if plugin is active
    In WordPress admin > Plugins, verify whether the Pexels plugin is currently activated
    Affected if Plugin is active and can make HTTP requests
  4. Inspect plugin for URL handling functionality
    Access the plugin settings page and review any features that accept or process URLs, such as image search or API configuration fields
    Affected if Plugin contains input fields that accept URLs for server-side processing

If the Raajtram Pexels plugin version 1.2.2 or lower is installed and active with URL-handling features enabled, the environment is affected by this SSRF vulnerability

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 1.2.2
Interim mitigation

Implement strict URL allowlisting and validate all user-supplied URLs before making server-side requests, restricting destinations to trusted domains only; disable unnecessary URL protocols and ensure proper input sanitization.

Recommended fix Moderate confidence

Update to the latest version available in the WordPress plugin repository (check wordpress.org for the current stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Pexels: Free Stock Photos' plugin
  4. Check if an update is available (compare current version 1.2.2 with the latest version shown)
  5. If a newer version is available, click 'Update Now' to upgrade to the latest version
  6. After updating, verify the plugin is functioning correctly by testing photo searches

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

Fix this in Pexels\ Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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 locally
dbcve dependency scanner

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