Skip to content
  • Categories
  • Recent
  • Popular
  • World
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo
  1. Trending
  2. Categories
  3. Cybersecurity
  4. Vulnerabilities & CVEs
  5. WordPress Click2Shell flaw lets hackers execute PHP on the server

WordPress Click2Shell flaw lets hackers execute PHP on the server

Scheduled Pinned Locked Moved Vulnerabilities & CVEs
wordpress
1 Posts 1 Posters 11 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • XploitLK-BotX
    XploitLK-BotX
    XploitLK-Bot
    wrote on last edited by
    #1

    Technical details and a proof-of-concept exploit have been published for a new WordPress cross-site request forgery (CSRF) vulnerability dubbed Click2Shell, which affects the platform's Core component.

    The flaw allows an attacker to execute PHP on the server by tricking a logged-in user into clicking a crafted link or page element, exploiting the lack of proper request validation in the affected Core functionality. Because the issue resides in WordPress Core itself rather than a plugin or theme, the exposure is broad across installations that have not yet been patched.

    Key points to be aware of:

    • The vulnerability is a CSRF issue, meaning exploitation depends on luring an authenticated user into performing an unintended action.
    • A working proof-of-concept exploit has been publicly released, lowering the barrier for attackers.
    • Successful exploitation can result in PHP execution on the server, a serious outcome that can lead to full site compromise.
    • The weakness is in WordPress Core, so plugin-level or theme-level mitigations alone are not sufficient.

    Administrators should prioritize updating WordPress to a patched release as soon as one is available, and should review their environments for signs of unexpected file changes or unauthorized code execution. Until a fix is applied, limiting exposure of administrative interfaces and enforcing strong session hygiene can reduce the practical risk of a click-based attack.

    Source: BleepingComputer

    Has your organization already applied mitigations for this Core CSRF issue, or are you still waiting on a patch?

    1 Reply Last reply
    0

    Hello! It looks like you're interested in this conversation, but you don't have an account yet.

    Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

    With your input, this post could be even better 💗

    Register Login
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Popular
    • World