CVE and update status of the FreeBSD ports tree3,576 unaddressed CVEs in 729 portsAll times are CET
CVE details

CVE-2026-119977

WordPress Core is vulnerable to Remote Code Execution in versions 4.7 through 7.1.3. This is due to predictable, web-accessible staging paths used during full-package core upgrades. This makes it possible for unauthenticated attackers to execute code on the server during the upgrade window.

Score
8.1 high
Published
2026-10-31
Links
NVD · cve.org · Report wrong data

Matched ports (4)

PortPackageVersionStatusMaintainer
french/wordpressfr-wordpress-fr_FR7.1.3_2,1unaddresseddelphij@FreeBSD.org
japanese/wordpressja-wordpress-ja7.1.3unaddresseddelphij@FreeBSD.org
russian/wordpressru-wordpress-ru_RU7.1.3_1unaddresseddelphij@FreeBSD.org
www/wordpresswordpress7.1.3,1unaddresseddelphij@FreeBSD.org

Template for a VuXML entry

Check the content

Check the version numbers before you commit this entry. Some ports share an entry in the CVE database with another port, such as sqlite2 and sqlite3. The version shown here may then be one that never existed for this port.

Ranges per package from the CVE rows that match this port, in pkg notation with the port's epoch and revision, every bound checked with pkg; one range per epoch the port actually had. make newentry in security/vuxml creates the vid.

  <vuln vid="FIXME (make newentry)">
    <topic>fr-wordpress-fr_FR -- FIXME</topic>
    <affects>
      <package>
	<name>fr-wordpress-fr_FR</name>
	<range><ge>7.1.0,1</ge><le>7.1.3_2,1</le></range>
      </package>
      <package>
	<name>ja-wordpress-ja</name>
	<range><ge>7.1.0</ge><le>7.1.3</le></range>
      </package>
      <package>
	<name>ru-wordpress-ru_RU</name>
	<range><ge>7.1.0</ge><le>7.1.3_1</le></range>
      </package>
      <package>
	<name>wordpress</name>
	<range><ge>7.1.0,1</ge><le>7.1.3,1</le></range>
      </package>
    </affects>
    <description>
      <body xmlns="http://www.w3.org/1999/xhtml">
	<p>CVE-2026-119977: WordPress Core is vulnerable to Remote Code Execution
	  in versions 4.7 through 7.1.3. This is due to predictable, web-
	  accessible staging paths used during full-package core upgrades.
	  This makes it possible for unauthenticated attackers to execute
	  code on the server during the upgrade window.</p>
      </body>
    </description>
    <references>
      <cvename>CVE-2026-119977</cvename>
      <url>https://nvd.nist.gov/vuln/detail/CVE-2026-119977</url>
    </references>
    <dates>
      <discovery>2026-10-31</discovery>
      <entry>2026-10-31</entry>
    </dates>
  </vuln>